What this category's data looks like
This page focuses on the foreign teacher appointment and course scheduling category. The materials include three types: appointment contracts, work permit materials, and course schedules. Appointment contracts provide the teacher's name, position, appointment period, and signature field; work permit materials provide the document number, permit date, and receipt; course schedules provide the course name, week number, class hours, and assigned teacher. The three types of materials are updated weekly; appointment changes are synchronized with contract signing, permit progress is returned with receipts, and course adjustments are revised with the scheduling table. When the materials enter the tool call node, the contract and permit are used to verify identity and term, and the course schedule is used to verify class hours and teacher matching. Together, the three support the field sources of the progress table and the statistical scope description. The field characteristics are four types: name, quantity, date, and signature. It often occurs that the same record has inconsistent name spellings, quantity totals, or date order across different materials, with versions not synchronized or missing signature receipts.
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), 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. Based on the tool introduction, parameter introduction, 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 |
|---|---|---|
| Appointment contract | Check whether the contract fields, dates, and signature are consistent with the work permit materials and course schedule | Open the contract and compare item by item the name, position, appointment start and end, and signature field; check the date order and whether receipts are complete |
| Work permit materials | Check whether the permit fields, dates, and receipt are consistent with the appointment contract and course schedule | Verify the document number, permit date, and receipt; confirm there is no conflict with the contract appointment period; check whether the version is synchronized |
| Course schedule | Check whether the course fields, week numbers, and class hours are consistent with the appointment contract and work permit materials | Compare the course name, week number, class hours, and assigned teacher; check the quantity and dates of the same record in the two materials |
| Tool call node | Check whether the tool introduction, parameter introduction, and whether required correspond to the business material fields | On the canvas, check the diamond connectors and node status; test-run with a question missing a required parameter; inspect toolChoice, functionCall, and the call record |
Three common errors
- Symptom: the same teacher's name is written differently in the contract and the course schedule, and the class hour totals do not match. Cause: the two materials are entered separately, without field-level comparison and version synchronization.
- Symptom: the work permit materials lack a receipt or the contract lacks a signature, but the progress table still records it as complete. Cause: during verification, only the quantity was checked, not the signature and receipt status, and exceptions were not written into the scope.
- Symptom: values that do not exist in the business materials appear in the returned result, or the model answers directly without calling the tool. Cause: the parameter introduction and whether required do not correspond to the material fields, and the prompt does not guide follow-up questions.
How to verify the setup
Acceptance of this feature: test-run 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 question or calls according to the introduction; at the same time, check whether toolChoice and functionCall appear, and whether the tool introduction and parameter introduction can be understood on their own.
Business test: use one week of records to verify the totals, see whether the scope and exceptions are clearly written, whether the record count and statistical count match, and whether the scope is written in the header.
- Open the parameter configuration one by one, check the two items of introduction and whether required, and confirm they correspond to fields that actually exist in the appointment contract, work permit materials, and course schedule.
- On the canvas, check the diamond connectors and node status, and check whether the tool call node is connected to the target tool, to avoid results interfering with each other after multiple tools are connected in series.