What this category's data looks like
This page is intended for primary and secondary school enrollment organizations. The materials come from three core documents: the enrollment plan, the application materials checklist, and the admission list, updated weekly and summarized monthly. The enrollment plan provides batches and time nodes, the application materials checklist carries student information and attachment receipts, and the admission list records the final destinations and signature status. When the materials enter the tool calling and plugin feature, each has a different role: the enrollment plan is used to compare batch dates, the application materials checklist is used to check field completeness, and the admission list is used to verify quantities and signature receipts. The names, quantities, and dates of the three materials must be aligned item by item in the progress table and the statistical scope description, with the scope written into the header and exceptions marked separately.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the inputs and returns in the call record). The "progress table and statistical scope description" is then completed by a subsequent AI node or manual verification. Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to call the tool this time.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Whether the batch, date, and signature fields are consistent with the application materials checklist, and whether the plan version is synchronized | Open the tool node description field, check the batch dates in the plan against the checklist receipt dates, and check whether the inputs of toolChoice and functionCall in the call record are taken from the original plan text |
| Application materials checklist | Whether student names, quantities, and attachment receipts match the admission list, and whether missing signatures or receipts are marked | Open the parameter configuration one by one, check the two items of description and whether required, run a trial with a question missing a required field, and see whether the call record returns a follow-up question first rather than directly fabricating |
| Admission list | Whether the admission quantity, date, and signature status are consistent with the header of the statistical scope description, and whether the version is synchronized | Check the diamond connectors and node status on the canvas, and check whether values that do not exist in the list appear in the toolChoice return result |
| Progress table and statistical scope description | Whether the record count and statistical count match, whether the scope is written into the header, and whether exceptions are clearly stated | Use one week of records to check the total, compare the names, quantities, and dates of the three materials, and confirm that the functionCall call record is consistent with the header scope |
Three common errors
- Symptom: The name, quantity, and date of the same student do not match between the application materials checklist and the admission list. Cause: The versions of the two materials are not synchronized, and the tool call return result has not undergone field-level comparison.
- Symptom: The admission list is missing a signature or receipt, but the statistical total is still counted at the original number. Cause: The scope is not written into the header, and exceptional cases are not marked separately in the progress table.
- Symptom: The model does not call the tool and directly gives an answer, and values that do not exist in the business materials appear in the return result. Cause: The tool description and parameter descriptions do not clearly state the purpose and values, and required parameters lack prompt guidance.
How to verify the setup
Acceptance of this feature: run a trial with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks a follow-up question or calls according to the description; at the same time, check the source of the values of toolChoice and functionCall in the call record, and confirm that fields that do not exist in the materials have not been fabricated.
Business test: use one week of records to check the total, see whether the scope and exceptions are clearly stated, and compare the names, quantities, dates, and signature receipts of the three materials: the enrollment plan, the application materials checklist, and the admission list.
- Open the tool node description field, check whether the description can be understood when taken out on its own, and check whether the two items of parameter description and whether required correspond to the business material fields.
- Check the diamond connectors and node status on the canvas, run a trial with a question missing a required field, and confirm that the call record asks a follow-up question first rather than directly fabricating parameter values.