What this category's data looks like
This page focuses on primary and secondary school student status establishment and changes. Materials come from three categories: student status archives, transfer applications, and suspension/resumption materials. Student status archives are the base ledger of student identity and enrollment status, with fields including name, student status number, class, enrollment date, and signature; transfer applications record cross-school movement, with fields including transferring-out school, transferring-in school, application date, signatures of both parties, and receipt; suspension/resumption materials record status interruption and restoration, with fields including suspension start and end, resumption date, and approval signature. Materials are updated by semester and change event. The same record often appears in two materials with inconsistent names, quantities, or dates, versions not synchronized, and missing signatures or receipts. When entering this feature, student status archives serve as the baseline ledger, transfer applications and suspension/resumption materials serve as sources to be verified, and the three together support discrepancy localization.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the input parameters and return in the call record). The "discrepancy list" 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; when there are no required parameters, the model may fabricate parameter values on its own, and when there are required parameters but no suitable value in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Student status archives | Fields, dates, and signatures are complete, and the names of records with the same name in transfer applications and suspension/resumption materials are consistent | Open the tool node description fields and check whether name, student status number, and enrollment date are readable; open each parameter configuration one by one and check the two items description and whether required; check the diamond connectors and node status on the canvas, and confirm the toolChoice and functionCall call paths |
| Transfer applications | Names, quantities, and dates are consistent with the student status archive baseline ledger, and signatures of both parties and receipt are not missing | Run a test with a question missing the transferring-out school field and see whether it asks a follow-up first instead of directly fabricating; check whether values that do not exist in the business materials appear in the returned result; check whether results from multiple tools connected in series interfere with each other |
| Suspension/resumption materials | Suspension start and end and resumption date are consistent with the student status archive status fields, and approval signature is not missing | Open each parameter configuration one by one and check the two items description and whether required; run a test with a question missing the resumption date, check the input parameters and return in the call record, and confirm whether it asks a follow-up or calls according to the description |
| Tool call node | The diamond interface is connected to the target tool, and the node status and connectors are readable | Check the diamond connectors and node status on the canvas; check whether the tool description can be understood when taken out alone; check whether the two items parameter description and whether required correspond to the business material fields |
Three common errors
- Symptom: the same student's name, class, or enrollment date does not match between the student status archive and the transfer application. Cause: the two materials were entered at different times, versions are not synchronized, and fields have not been uniformly checked.
- Symptom: suspension/resumption materials lack an approval signature or receipt, and transfer applications lack the transferring-in school's stamp. Cause: the material circulation step is not closed-loop, and signatures and receipts are not archived together with the record.
- Symptom: the model does not call the tool and directly gives an answer, or values that do not exist in the business materials appear in the returned result. Cause: the tool description and parameter descriptions do not clearly state the purpose and values, and required parameters are not guided by prompts.
How to verify the setup
This feature's acceptance: run a test with a question missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up or calls according to the description; at the same time check the behavior of toolChoice and functionCall in the call record, and check that the tokens of the quoted text and the number of array items are recorded separately.
Business test: use a real record to find fields inconsistent with the ledger, check whether the names, quantities, and dates of the same object in the two materials are consistent, submit to the reviewer for confirmation and write back.
- Open the tool node description fields, check whether this description can be understood when taken out alone, and state the purpose, when it should be used, and what result it returns.
- Open each parameter configuration one by one and check the two items description and whether required; run a test with a question missing that field and see whether it asks a follow-up first instead of directly fabricating.