What this category's data looks like
This page focuses on the compulsory education dropout prevention and control category. The materials include dropout risk ledgers, return-to-school persuasion records, and home visit records. The sources are submissions from schools and townships, updated weekly and archived monthly. The ledger uses students as rows and risk levels and dates as columns. Persuasion records include the persuader, time, signature, and receipt. Home visit records include the visitor, date, and parent signature. When entering the Q&A intake and missing-item follow-up function, the ledger carries risk clues and identity fields, persuasion records carry process and result fields, and home visit records carry supporting evidence and signature fields. The fields of the three types of materials intersect, and dates and signatures are the key points for verification.
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). "Intake records and completed question items" are then completed by subsequent AI nodes 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 |
|---|---|---|
| Dropout risk ledger | Fields include student name, risk level, and date; the name, quantity, and date of the same record do not match across the two materials | Open the tool node description fields, check the parameter descriptions and whether they are required; run a test question with a missing risk level field to see whether it asks a follow-up question first |
| Return-to-school persuasion record | Fields include persuader, time, signature, and receipt; if the signature or receipt is missing, it is treated as a missing item | Open each parameter configuration one by one, check the description and whether it is required; check the diamond-shaped connections and node status on the canvas |
| Home visit record | Fields include visitor, date, and parent signature; if the version is not synchronized, the date and signature are inconsistent | Verify the input parameters and return of toolChoice and functionCall in the call record, and confirm whether it asks a follow-up question or calls according to the description |
| Tool call node connections | The diamond-shaped interface is connected to the target tool, and the node status is readable | Check the diamond-shaped connections and node status on the canvas, and verify the call records of toolChoice and functionCall |
Three common errors
- Phenomenon: the name, quantity, and date of the same record do not match across the two materials. Cause: the ledger and return-to-school persuasion records are entered separately, and no cross-check of fields was performed.
- Phenomenon: the version is not synchronized, and the date in the home visit record is inconsistent with the date in the return-to-school persuasion record. Cause: materials are updated weekly, and versions were not unified during archiving.
- Phenomenon: when the signature or receipt is missing, the model directly gives an answer. Cause: required parameters were not guided in the prompt to ask follow-up questions, and the model fabricated parameter values on its own.
How to verify the setup
Acceptance for this function: run a test question that lacks required parameters, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the description; verify the call records of toolChoice and functionCall.
Business test: ask a question that lacks key information and see whether it asks a follow-up question before answering.
- Open the tool node description fields and check whether this description can be understood on its own.
- Open each parameter configuration one by one, check the description and whether it is required, and run a test question that lacks that field.