What this category's data looks like
This page centers on general college entrance examination registration qualification review, focusing on field verification and discrepancy localization across three types of materials: the registration form, household registration and student status certificates, and materials for children accompanying migrant workers. The registration form is entered by the candidate or the registration point, and contains name, ID number, graduating school, examination subject category, and a signature field; household registration and student status certificates are issued by the public security authorities and the school, and contain household registration address, date of move-in, student status start and end dates, and a seal; materials for children accompanying migrant workers contain residence permits, social insurance payment records, parents' employment certificates, and receipts. The three types of materials are submitted together by registration batch, field formats and date notations are not uniform, and signature and receipt locations are scattered. When entering this feature, the registration form serves as the main record, while household registration and student status certificates and materials for children accompanying migrant workers serve as comparison sources, used to locate whether the name, quantity, and date of the same object are consistent across the two materials, and to flag fields whose versions are not synchronized or that are missing signatures or receipts.
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 inputs and returns in the call record). The discrepancy list is then completed by a subsequent AI node 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; when multiple tools are chained, toolChoice and functionCall determine the call path, and the call record retains the inputs and returns for review.
| Object | Check | Verification action |
|---|---|---|
| Registration form for the general college entrance examination | Check whether the name, quantity, date, and signature field correspond to the household registration and student status certificates and the materials for children accompanying migrant workers | Open the tool node description field and check whether the purpose and return results are stated; run a test with a question missing a required parameter to see whether it asks a follow-up question first |
| Household registration and student status certificates | Check whether the household registration address, date of move-in, student status start and end dates, and seal are consistent with the registration form | Open each parameter configuration and check the two items: parameter description and whether it is required; check the diamond-shaped connections and node status on the canvas |
| Materials for children accompanying migrant workers | Check whether the dates and signatures of the residence permit, social insurance records, parents' employment certificates, and receipts are complete | Run a test with one real record and check whether the return result contains values that do not exist in the business materials |
| Tool calling node | Check whether the tool description, parameter descriptions, and whether parameters are required correspond to the business material fields | Check the call records of toolChoice and functionCall to confirm that the inputs and returns are traceable |
Three common errors
- Symptom: The same candidate's name is written differently in the registration form and the household registration and student status certificates, and the dates do not match. Cause: The two materials have different entry sources, field formats are not unified, and the model directly returns the comparison result after calling according to the description.
- Symptom: The residence permit and social insurance records in the materials for children accompanying migrant workers are not synchronized in version, and the receipt is missing. Cause: The materials are submitted in batches, and the tool calling node does not ask a follow-up question based on whether parameters are required, but directly calls according to the description.
- Symptom: The return result contains values that do not exist in the business materials. Cause: When there are no required parameters, the model fabricates parameter values on its own, and the inputs in the call record are inconsistent with the actual material fields.
How to verify the setup
Feature acceptance: run a test with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks a follow-up question or calls according to the description; at the same time, check whether the call paths of toolChoice and functionCall are traceable.
Business test: use one real record to find fields inconsistent with the ledger, and confirm whether missing items in name, quantity, date, and signature are marked in the discrepancy list.
- Open the tool node description field, check whether this description can be understood when read on its own, and check whether the two items, parameter description and whether it is required, correspond to the business material fields.
- On the canvas, check whether the diamond-shaped interface is already connected to the target tool, and run a test with a question missing that field to see whether it asks a follow-up question first instead of directly fabricating.