What this category's data looks like
This page is intended for primary and secondary school enrollment organizations. The materials come from enrollment plans, application material checklists, admission lists, and receipt ledgers, and are updated intensively by enrollment season and revised in rolling batches. The enrollment plan contains the enrollment scope, time nodes, and signature fields; the application material checklist contains student names, ID numbers, material items, and quantities; the admission list contains admission sequence numbers, names, dates, and confirmation signatures. When these three types of materials enter this feature, the enrollment plan serves as the rule baseline, the application material checklist serves as the details to be verified, and the admission list and receipts serve as the comparison results. The tool call node accordingly verifies names, quantities, dates, and signatures field by field, and outputs discrepancy clues for subsequent review.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), and outputs the tool call result (the inputs and returns 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.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Check whether the enrollment scope, time nodes, signature fields, and version number are consistent with the application material checklist | Open the tool node description field and confirm that the purpose and return result can be understood on their own; on the canvas, verify that the diamond interface is connected to the target tool, and check the connection status related to toolChoice |
| Application material checklist | Check whether the same student's name, ID number, number of material items, and date correspond one by one with the admission list | Open each parameter configuration one by one, and check the two items: parameter description and whether it is required; run a trial with a question missing a required field, and observe whether it asks a follow-up question first |
| Admission list | Check whether the admission sequence number, name, date, confirmation signature, and receipt are complete and version-synchronized | Use one real record to compare ledger fields, and record differences between inputs and returns; check whether the returned values in the functionCall call record come from the materials |
| Receipt ledger | Check whether signatures and receipts are missing, and whether dates are consistent with the admission list | Check the inputs and returns in the call record, mark records missing signatures or receipts, hand them to the reviewer for confirmation, and write them back |
Three common errors
- Symptom: the same student's name or ID number does not match between the application material checklist and the admission list. Cause: the two materials are entered separately, no field-level comparison is performed, and versions are not synchronized.
- Symptom: the number of material items or dates are inconsistent between the two materials, and receipts are missing. Cause: after rolling batch revisions, the ledger is not written back, and the signature fields are not updated synchronously.
- Symptom: values appear in the return result that do not exist in the business materials. Cause: when there are no required parameters, the model may fabricate parameter values on its own; when there are required parameters but no suitable value in the context, it may not call the tool.
How to verify the setup
Feature acceptance: run a trial with a question missing a required parameter, check the inputs and returns in the call record, confirm whether it asks a follow-up question or calls according to the description, and check toolChoice, functionCall, and the connection status of the tool call node.
Business test: use one real record to find fields inconsistent with the ledger, mark differences in name, quantity, date, or signature, hand them to the reviewer for confirmation, and write them back.
- Open each parameter configuration one by one, check the two items: parameter description and whether it is required, and confirm that they correspond to the business material fields.
- On the canvas, check the diamond connections and node status, run a trial with a question missing a field, and observe whether it asks a follow-up question first instead of directly fabricating.