What this category's data looks like
This page is intended for university admissions physical examination organization. The materials come from three types of documents: physical examination forms, re-examination applications, and restricted-major notifications. They are accepted centrally by admissions batch and updated in batches. Physical examination forms record height and weight, vision and color perception, past medical history, and physician signature, and are the primary basis for missing-item follow-up; re-examination applications record the application reason, original examination date, proposed re-examination items, and receipt, and are used to identify missing dates and items; restricted-major notifications record the restricted major name, basis for restriction, notification date, and candidate signature, and are used to check names and quantities. When these three types of materials enter the Q&A intake and missing-item follow-up function, they respectively serve as the master file, trigger document, and notification evidence, with fields using name, quantity, date, and signature as verification anchors.
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). "Intake records and completed question items" are then completed by subsequent AI nodes 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.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Whether name, quantity, date, and signature are complete; if any item is missing, follow-up questions must be asked first | Open the tool node introduction fields, run a trial with a question missing required parameters, and check the input parameters and return in the call record |
| Re-examination application | Whether the application reason, original examination date, proposed re-examination items, and receipt match | Open each parameter configuration one by one, check the two items of parameter introduction and whether required, and check the functionCall return |
| Restricted-major notification | Whether the restricted major name, basis for restriction, notification date, and candidate signature are consistent | Check the diamond connectors and node status on the canvas, and confirm that toolChoice and functionCall point to the target tool |
| Version and receipt | Whether the version and receipt of the same record in the two materials are synchronized | Compare the name, quantity, and date in the two materials; mark as pending supplementation when signature or receipt is missing |
Three common errors
- Symptom: the same candidate's name or quantity does not match in the two materials. Cause: during entry, the physical examination form master file was not used as the baseline, and the re-examination application and notification were each written separately.
- Symptom: the date of the restricted-major notification is earlier than the date of the re-examination application. Cause: the version was not synchronized, the old notification was not updated with the re-examination result, and the signature field is blank.
- Symptom: values that do not exist in the materials appear in the call return. Cause: this parameter has no required constraint, the model fabricates parameter values on its own, and does not ask follow-up questions first.
How to verify the setup
Acceptance of this function: run a trial with a question missing required parameters, check the input parameters and return in the call record, and confirm whether it asks follow-up questions or calls according to the introduction; check whether toolChoice and functionCall point to the target tool, and whether the return contains values outside the materials.
Business test: ask a question missing key information and see whether it asks follow-up questions before answering.
- Check the tool introduction fields and confirm that they state the purpose, when it should be used, and what result is returned, and that they can be understood when read on their own.
- Open each parameter configuration one by one, check the two items of parameter introduction and whether required, and run a trial with a question missing that field to see whether it asks follow-up questions first.