What this category's data looks like
This category's data consists of vocational college program setup filing materials, including three types: the program setup filing form, the talent demand justification, and the faculty and equipment list. The source is the filing documents and accompanying supporting materials submitted by the institutions, and the update cadence changes with the application batches and correction rounds. Field characteristics center on the program name, enrollment number, number of faculty, number of equipment units, justification date, and signature field. When the program setup filing form enters this function, it serves as the main record and provides the baseline for the program name and date; the talent demand justification serves as the justification basis and provides industry research and job correspondence relationships; the faculty and equipment list serves as conditional material and provides quantity and signature information. After the materials enter the tool calling node, the model decides whether to call a tool based on the tool description, parameter descriptions, and whether it is required.
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), and outputs the tool call result (the inputs and returns in the call record). "Acceptance records and items to be completed" is then handled by subsequent AI nodes or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Program setup filing form | Whether the fields, date, and signature are complete, and whether the program name and enrollment number are consistent with the talent demand justification | Open the tool node description field and check whether the description can explain its purpose, when it should be used, and what it returns; run a test with a question missing a required parameter and observe the functionCall and toolChoice records |
| Talent demand justification | Whether the justification date and signature are present, and whether the job names and quantities correspond to the filing form | Open each parameter configuration one by one and check the two items: the parameter description and whether it is required; compare the names, quantities, and dates of the same record in the two materials |
| Faculty and equipment list | Whether the number of faculty and the number of equipment units are consistent with the filing form, and whether the signature or receipt is missing | Check the diamond-shaped connections and the tool calling node status on the canvas, and confirm that after toolChoice is triggered, the returned result does not contain values that do not exist in the materials |
| Acceptance records and items to be completed | Whether missing items are identified and followed up on, and whether the answer cites material fields | Run a test with a question missing key information, check the inputs and returns in the call record, and confirm whether it is a follow-up question or a call according to the description |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the filing form and the talent demand justification. Cause: The versions of the two materials are not synchronized, and the parameter descriptions are not aligned with the business fields.
- Symptom: Values that do not exist in the materials appear in the returned result. Cause: When there are no required parameters, the model fabricates parameter values on its own, and the parameter descriptions do not specify the source of the values.
- Symptom: The faculty and equipment list is still treated as complete material even though the signature or receipt is missing. Cause: Whether it is required does not correspond to the signature field, and the model does not follow up.
How to verify the setup
Acceptance of this function: run a test with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it is a follow-up question or a call according to the description; at the same time, check the behavior of functionCall and toolChoice in the record.
Business test: ask a question missing key information, see whether it follows up first before answering, and check whether the answer cites fields from the program setup filing form, the talent demand justification, and the faculty and equipment list.
- Open the tool node description field, check whether this description can be understood when taken out on its own, and check the two items: the parameter description and whether it is required.
- Check the diamond-shaped interface connections and the tool calling node status on the canvas, and confirm that the inputs and returns in the call record do not contain fabricated values.