What this category's data looks like
In the scenario of primary and secondary school timetables and after-school service scheduling, progress records and statistics verification involve three types of materials: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable is finalized at the start of the semester and records class, period, week, and venue; the teacher assignment table is updated weekly and records teacher name, subject, class, and number of class hours; the after-school service project table rolls over by project cycle and records project name, number of participants, date, and signature field. When these three types of materials enter tool calling and plugin functions, the master timetable serves as the baseline reference, the teacher assignment table serves as the source for class-hour statistics, and the after-school service project table serves as the basis for exception and receipt verification. Materials are uploaded as tables or scanned receipts, the update rhythm is weekly and monthly in parallel, and fields include name, quantity, date, signature, and version number.
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 input parameters and return in the call record). The "progress table and statistical scope description" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields include class, period, week, venue, and signature field; the date and version number must be consistent with the teacher assignment table | Check whether the class names, number of periods, and dates in the master timetable and the teacher assignment table match item by item, and check the signature and version number |
| Teacher assignment table | Fields include teacher name, subject, class, number of class hours, and week; the name and quantity of the same record in the two materials must be consistent | Use one week's records to check the total class hours line by line, and confirm that the teacher name and class name can find corresponding entries in the master timetable |
| After-school service project table | Fields include project name, number of participants, date, and receipt signature; exceptions must be noted in the header scope | Check whether the project name and number of participants are consistent with the receipt, check whether the date and signature field are missing items, and mark records whose versions are not synchronized |
| Tool calling node | The tool introduction states the purpose, when it should be used, and what result it returns; the parameter introduction and whether it is required are checked item by item | Open the tool node introduction field and parameter configuration, check the diamond-shaped connections and node status on the canvas, and test-run with a question that lacks a required parameter |
Three common errors
- Symptom: The class name and number of class hours of the same record do not match between the master timetable and the teacher assignment table. Cause: The two materials have different update rhythms, versions are not synchronized, and there is no unified scope description.
- Symptom: The date in the after-school service project table is inconsistent with the receipt date, and the signature field is blank. Cause: The receipt was not collected in time, and the project table was filled in according to the planned date rather than corrected to the actual execution date.
- Symptom: The returned result contains values that do not exist in the business materials, or the model does not call the tool and directly gives an answer. Cause: Parameters are not marked as required or the introduction description is unclear, and the model fabricates parameter values based on context.
How to verify the setup
Acceptance of this feature: test-run with a question that lacks a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the introduction; check the three items of tool introduction, parameter introduction, and whether required, check the values of toolChoice and functionCall in the call record, and confirm whether toolChoice triggers the call and whether the functionCall return contains values that do not exist in the materials.
Business test: use one week's records to check the total, and see whether the scope and exceptions are clearly written; check the fields, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table, and confirm that the number of records matches the statistical count.
- Open the tool node introduction field and check whether this description can be understood when taken out on its own; open the parameter configuration one by one, check the two items of introduction and whether required, and test-run with a question that lacks that field to see whether it asks a follow-up question first.
- Check the diamond-shaped connections and node status on the canvas, and confirm that the tool calling node is connected to the target tool; use one week's records to check the total, check whether the header scope and exceptions are clearly written, and mark records missing signatures or receipts.