What this category's data looks like
This page addresses the scenario of vocational school student internship management. Materials include three types: internship agreements, internship plans, and internship logs. Internship agreements are signed by three parties: the school, the enterprise, and the student, and contain position, term, insurance, signature fields, and receipt; internship plans are submitted by supervising teachers and contain batch, number of people, start and end dates, and approval signature; internship logs are filled in by students on a weekly basis and contain date, position, tasks, and mentor signature. The three types of materials are updated by batch and week, and the fields are mainly name, quantity, date, and signature status. When entering this function, agreements and plans serve as baseline materials, logs serve as materials to be verified, and the tool calling node pulls and compares field by field, outputting the inputs and returns in the call records for subsequent nodes or manual discrepancy localization.
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 results (the inputs and returns in the call records). The "discrepancy list" is completed next 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.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether the name, quantity, date, and signature fields are consistent in the two materials | On the canvas, check the diamond connectors and node status, confirm that the tool calling node is connected to the agreement field reading tool, and inspect the call records corresponding to toolChoice and functionCall |
| Internship plan | Whether the batch, number of people, start and end dates, and approval signature match the agreement | Open the parameter configuration one by one, check the description and whether it is required, and run a test with a question missing that field to see whether it asks a follow-up question first |
| Internship log | Whether the date, position, tasks, and mentor signature correspond week by week to the plan | Compare the inputs and returns in the call records, and mark fields whose name, quantity, or date do not match between the two materials in the same record |
| Discrepancy list | The name, quantity, and date of the same object are consistent in the two materials | Hand the tool call results to the reviewer for confirmation; after confirmation, write back to the ledger and record the version |
Three common errors
- Symptom: the dates of the same record in the agreement and the log do not match. Cause: the two materials are updated by different batches, and the tool call only retrieved the field value from one of them.
- Symptom: values appear in the returned results 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 records do not match the actual materials.
- Symptom: logs missing a signature or receipt are still marked as verifiable. Cause: the required item does not correspond to the signature field, and the model calls according to the description without asking a follow-up question first.
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 records, and confirm whether it asks a follow-up question or calls according to the description; at the same time, check the values of toolChoice and functionCall in the call records.
Business test: use a real record to find fields inconsistent with the ledger, mark at least one discrepancy in name, quantity, or date, and hand it to the reviewer for confirmation.
- Open the tool node description field, check whether this description can be understood when taken out on its own, and confirm that the diamond interface is connected to the target tool.
- Open the parameter configuration one by one, check the description and whether it is required, and run a test with a question missing that field to see whether it asks a follow-up question first.