What this category's data looks like
This page focuses on three types of materials for primary and secondary school admissions organizations: admission plans, application material checklists, and admission lists. Admission plans are published annually by the education authorities and include admission scope, time nodes, and procedures; application material checklists are updated by the school admissions office before the application season and list the names, number of copies, and signature requirements for proofs such as household registration, property, and student status; admission lists are confirmed by the admissions leadership group after review and include student names, admission batches, and receipt status. When these three types of materials enter the Q&A intake and missing-item follow-up function, the admission plan serves as the rule basis for answering eligibility and timing questions, the application material checklist serves as the missing-item determination baseline for item-by-item comparison, and the admission list serves as the result query source for checking names and batches. The material update rhythm is annual updates for plans, quarterly adjustments for checklists, and batch synchronization for lists, and the field characteristics are multi-table intersection with dates and signatures coexisting.
Configuration and implementation checks
This part 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 intake records and the completed follow-up questions are then handled by subsequent AI nodes or manual verification. The model judges whether to call the tool this time based on the tool description, parameter description, and whether the parameter is required; 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 |
|---|---|---|
| Admission plan | Check whether the application date, admission scope, and signature field in the plan are consistent with the checklist | Open the tool node description field and check whether the description can independently explain the purpose and return; check the parameter description and whether it is required |
| Application material checklist | Check whether the name, number of copies, signature, and receipt requirements of each material in the checklist correspond to the plan | Run a test with a question missing a key field and see whether the tool calling node asks a follow-up first instead of directly fabricating; check the toolChoice and functionCall related configurations |
| Admission list | Check whether the name, admission batch, date, and receipt status in the list are consistent with the checklist | Check the diamond-shaped connections and node status on the canvas, and confirm that the tool calling node is connected to the target tool |
Three common errors
- Symptom: the same student's name or batch does not match between the application material checklist and the admission list. Cause: the two material versions are not synchronized, and different update rhythms lead to inconsistent field values.
- Symptom: the application date in the admission plan is inconsistent with the date in the checklist. Cause: after the annual plan update, the checklist was not adjusted in sync, and the date field was not cross-checked.
- Symptom: the application material checklist lacks a signature or receipt field, but the tool calling node still returns a complete result. Cause: the parameter was not marked as required, so the model called directly according to the description and fabricated the missing value.
How to verify the setup
This function'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 toolChoice, functionCall, and the connection status of the tool calling node.
Business test: ask a question missing key information and see whether it asks a follow-up before answering.
- Open the tool parameter configurations one by one, check the parameter description and whether it is required, and confirm that the required items correspond to fields that actually exist in the business materials.
- Check the diamond-shaped interface connections and the tool calling node status on the canvas, and confirm that the tool calling node is connected to the target tool and that the returned results are not mixed up.