What this category's data looks like
Kindergarten home-school co-education communication materials include teacher observation records, parent feedback forms, notification delivery receipts, and commitment item ledgers. These materials are updated weekly or by activity milestone, with fields including child name, date, commitment item, response time, description of child performance, category of parent request, and notification delivery status. When the materials enter the tool calls and plugins feature, the tool call node is responsible for initiating calls according to the tool introduction and parameter configuration, returning input parameters and return records; subsequent AI nodes or manual verification use these to form a discrepancy list, which is handed to the reviewer for confirmation and write-back.
Configuration and implementation checks
This step is executed by the tool call 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 "discrepancy list" is then completed by subsequent AI nodes or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Commitment item ledger | Whether the commitment item and response time are consistent | Check the commitment item and response time fields, and check whether there are commitments without a response; inspect whether the input parameters of functionCall in the tool call record include the commitment number and date |
| Child observation record | Whether the description of child performance and the parent feedback form are consistent | Compare the performance description for the same child on the same date, and mark fields whose wording does not match the observation record; check whether toolChoice triggers the call according to the tool introduction |
| Parent feedback form | Whether the category of parent request corresponds to the notification delivery record | Check entries in the feedback that are not categorized, and verify the notification delivery status and request category fields; confirm that the functionCall return does not contain values outside the materials |
| Notification delivery receipt | Whether the notification delivery status and date are consistent | Check the delivery status and date item by item, and mark missing or contradictory items; inspect the tool call node connections and node status |
Three common errors
- Phenomenon: A commitment item is recorded in the ledger, but the response time is blank. Cause: When there are required parameters and the context has no suitable value, the model may not call the tool, and prompt guidance is needed to fill the gap.
- Phenomenon: The request category in the parent feedback form is empty or categorized incorrectly. Cause: The parameter introduction does not specify the values, so the model may fabricate parameter values, causing the returned result to be inconsistent with the materials.
- Phenomenon: The description of child performance is inconsistent with the observation record. Cause: After multiple tools are chained, results interfere with each other, or the model does not call the tool and directly gives an answer.
How to verify the setup
Acceptance for this feature: run a trial with a question missing required parameters, inspect the input parameters and return in the call record, confirm whether it asks a follow-up question or calls according to the introduction, and check whether the values of toolChoice and functionCall come from the materials.
Business test: use one real record to find fields inconsistent with the ledger, mark commitments without a response, wording inconsistent with the observation record, or uncategorized feedback, and hand it to the reviewer for confirmation and write-back.
- Open the tool node introduction field, check whether the description can be understood when taken alone, and verify the parameter introduction and whether it is required.
- On the canvas, check the diamond connections and node status, run a trial with a question missing fields, and confirm that it asks a follow-up question first rather than directly fabricating.