What this category's data looks like
Materials for progress records and statistical verification of social evaluation of vocational skill level certification come from the evaluation implementation plan, candidate registration forms, and assessor dispatch forms, updated by batch and certification cycle, with fields including candidate name, occupational direction, level, registration date, assessor name, dispatch date, signature, and receipt. The evaluation implementation plan provides the batch and occupational direction, the candidate registration form provides the number of registrations and candidate details, and the assessor dispatch form provides the assessor list and dispatch dates. When these three types of materials enter the tool call node, each plays a different role: the implementation plan is used to verify the batch definition, the registration form is used to verify the number of people and names, and the dispatch form is used to verify assessors and dates. Weekly or monthly reports require a progress table and a statistical definition note, with the definition written in the table header, and the record count and statistical count must match.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), outputting the tool call result (the input parameters and return in the call record). The "progress table and statistical definition note" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Whether the batch, occupational direction, level, date, and signature are consistent with the registration form definition | Open the implementation plan, verify the batch and occupational direction fields, then compare the date and signature item by item against the registration form |
| Candidate registration form | Whether the candidate name, number of registrations, registration date, and receipt match the dispatch form | Use the registration form to verify names and numbers item by item, then verify the date and receipt against the dispatch form, and check for missing signature items |
| Assessor dispatch form | Whether the assessor name, dispatch date, signature, and receipt match the implementation plan | Open the dispatch form, verify the assessor name and dispatch date, then verify the batch and signature against the implementation plan |
| Tool call node | Whether the tool introduction, parameter introduction, and whether it is required correspond to the material fields | On the canvas, verify the diamond connectors and node status, open each parameter configuration one by one, and verify the introduction and whether-required items |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the registration form and the dispatch form. Cause: The two materials are maintained separately and were not compared item by item under the same batch definition.
- Symptom: The implementation plan version is not synchronized, and the batch or occupational direction is inconsistent with the registration form. Cause: After updating, the related materials were not written back, and the version was not synchronized.
- Symptom: The registration form or dispatch form lacks a signature or receipt, but the statistical count still includes it. Cause: The signature and receipt were not verified first, and the exception items were not clearly stated in the table header definition.
How to verify the setup
This feature acceptance: Run a trial with a question missing a required parameter, verify the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the introduction; check the toolChoice and functionCall related configurations, verify whether toolChoice is triggered according to the introduction, and verify whether the functionCall return contains values that do not exist in the materials.
Business test: Use one week of records to verify the total, and see whether the definition and exceptions are clearly stated; verify the tokens of the quoted text, record the number of array items separately, quoteMaxToken is the quoted content budget, and the two are not compared for equality.
- Open the introduction field in the tool node one by one, check whether this description can be understood on its own, and verify the parameter introduction and whether-required items.
- Run a trial with a question missing that field, see whether it asks a follow-up question first rather than directly fabricating; on the canvas, verify the diamond connectors and node status.