What this category's data looks like
This page focuses on journal publication license and annual verification materials, sourced from three types: journal publication licenses, annual verification forms, and rectification reports, aggregated weekly or monthly. The license states the entity and publication scope, the verification form records annual items and quantities, and the rectification report corresponds to issues and receipts. When materials enter the tool call node, each serves as a field source: the license provides the name and date baseline, the verification form provides quantity and signature clues, and the rectification report provides exception and receipt clues. Field characteristics include name, quantity, date, signature, and receipt; it is common for the same record to have mismatched names, quantities, and dates across the three materials, unsynchronized versions, and missing signatures or receipts.
Configuration and implementation checks
The tool call node in the workflow (the model decides whether to call, the node executes) only outputs the tool call result (the inputs and returns in the call record); the progress table and statistical criteria description must be handled subsequently by a later AI node or manual verification. The model judges whether to call the tool this time based on the tool description, parameter description, and whether parameters are required; when there are no required parameters, the model may fabricate parameter values on its own, and when there are required parameters but no suitable values in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Name, date, and signature fields checked item by item against the verification form and rectification report | Open the tool node description fields and check whether the license name and date match the verification form; run a test query missing a required parameter to see whether it asks a follow-up question first; check the toolChoice and functionCall related configurations |
| Annual verification form | Quantity, date, and signature checked item by item against the license and rectification report | Open each parameter configuration and check the description and whether it is required; use one week of records to check the total and see whether quantities and dates match; confirm whether the functionCall return contains values outside the materials |
| Rectification report | Receipt, signature, and date checked item by item against the license and verification form | Check the diamond connectors and node status on the canvas; check whether receipts and signatures are complete; run a test query missing that field to see whether it asks a follow-up question first rather than fabricating directly |
| Tool call node connectors | Diamond interface is connected to the target tool | Check the diamond connectors and node status on the canvas; confirm that the inputs and returns in the toolChoice and functionCall call records are consistent |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the verification form. Cause: The versions of the two materials are not synchronized, and field sources are not checked item by item.
- Symptom: The rectification report lacks a signature or receipt, but the verification form records it as completed. Cause: The receipt was not backfilled, the signature column was not checked, and exceptions were not noted in the header criteria.
- Symptom: The model did not call the tool and directly gave an answer. Cause: The tool description does not state when it should be used, and required parameters lack prompt guidance.
How to verify the setup
Acceptance for this feature: run a test query 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; check the toolChoice and functionCall related records to see whether the return contains values outside the materials.
Business test: use one week of records to check the total and see whether the criteria and exceptions are clearly stated; check whether the record count and statistical count match and whether the criteria are written in the header.
- Open the tool node description fields, check whether the description can be understood when taken out on its own, and check the parameter description and whether it is required.
- Run a test query missing that field to see whether it asks a follow-up question first; check the diamond connectors and node status on the canvas.