What this category's data looks like
Off-campus training compliance filing and penalty response involves three types of materials: the school operating license, course filing materials, and fee disclosure. The school operating license comes from the approving authority, and its fields include institution name, address, validity period, operating content, and issuance date; course filing materials are submitted by the institution by class session, and their fields include course name, class hours, instructor, filing date, and review signature; fee disclosure comes from the institution's disclosure channels, and its fields include fee items, standards, refund rules, disclosure date, and receipt. The three types of materials are aggregated weekly or monthly and enter tool invocation and plugin nodes. The school operating license serves as the baseline for subject qualification, course filing materials serve as the source of course progress records, and fee disclosure serves as the source of the fee statistical basis. In terms of update cadence, the license is reissued after changes, course filing rolls forward by class session, and fee disclosure is refreshed monthly. In terms of field characteristics, names, quantities, dates, signatures, and receipts are the focus of reconciliation; the same record often has mismatched names, quantities, and dates across different materials, versions are not synchronized, and signatures or receipts are missing.
Configuration and implementation checks
This link is executed by the tool invocation node in the workflow (the model decides whether to invoke, and the node executes), outputting the tool invocation result (the input parameters and return in the invocation record). The "progress table and statistical basis description" is then completed by a subsequent AI node or manual reconciliation. Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to invoke the tool this time; 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 invoke.
| Object | Check | Verification action |
|---|---|---|
| School operating license | Fields include institution name, address, validity period, operating content, and issuance date, with complete signatures and receipts | Open the tool node description fields and check whether the license fields match the names and dates in the course filing materials and fee disclosure; check whether the functionCall invocation record input parameters contain the required fields |
| Course filing materials | Fields include course name, class hours, instructor, filing date, and review signature, with the version synchronized with the license | Open the parameter configuration one by one and check the two items of description and whether required; run a test with a question missing the review signature field to see whether it asks a follow-up question first; check whether the toolChoice invocation record return contains values that do not exist in the materials |
| Fee disclosure | Fields include fee items, standards, refund rules, disclosure date, and receipt, with quantities matching the course filing materials | Check the diamond connectors and node status on the canvas; reconcile the totals using one week of records to see whether the basis and exceptions are clearly stated; check whether the functionCall return result is mixed up with the course filing materials |
| Progress table and statistical basis description | The number of records matches the statistical count, the basis is written in the header, and exceptions are stated | Run a test with a question missing required parameters, check the input parameters and return in the invocation record, and confirm whether it asks a follow-up question or invokes according to the description; check the totals and the basis header |
Three common errors
- Symptom: the same record has mismatched names, quantities, and dates in the school operating license and the course filing materials. Cause: the two materials are filled in by different stages without cross-checking, and the tool invocation result directly enters the statistics.
- Symptom: the version of the course filing materials is not synchronized, and the old version lacks signatures and receipts. Cause: after the materials are updated, they do not re-enter the tool node, the invocation record still references the old version's input parameters, and the statistical basis continues to use the old version.
- Symptom: the model does not invoke the tool and directly gives an answer, and the return result contains values that do not exist in the business materials. Cause: the tool description or parameter descriptions are not clear enough, and the required parameters have no suitable values in the context.
How to verify the setup
Acceptance of this feature: run a test with a question missing required parameters, check the input parameters and return in the invocation record, and confirm whether it asks a follow-up question or invokes according to the description; at the same time, check whether the toolChoice and functionCall records are consistent with the three items of tool description, parameter descriptions, and whether required.
Business testing: reconcile the totals using one week of records to see whether the basis and exceptions are clearly stated; check whether the names, quantities, dates, signatures, and receipts of the school operating license, course filing materials, and fee disclosure match.
- Open the tool node description fields and check whether this description can be understood when taken out on its own; open the parameter configuration one by one and check the two items of description and whether required; run a test with a question missing that field to see whether it asks a follow-up question first rather than directly fabricating.
- Check the diamond connectors and node status on the canvas; reconcile the totals using one week of records to see whether the basis and exceptions are clearly stated; check whether the results are mixed up with each other after multiple tools are chained together.
This link is executed by the tool invocation node in the workflow (the model decides whether to invoke, and the node executes), outputting the tool invocation result (the input parameters and return in the invocation record). The "progress table and statistical basis description" is then completed by a subsequent AI node or manual reconciliation. Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to invoke the tool this time; 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 invoke.
- Symptom: the same record has mismatched names, quantities, and dates in the school operating license and the course filing materials. Cause: the two materials are filled in by different stages without cross-checking, and the tool invocation result directly enters the statistics.
- Symptom: the version of the course filing materials is not synchronized, and the old version lacks signatures and receipts. Cause: after the materials are updated, they do not re-enter the tool node, the invocation record still references the old version's input parameters, and the statistical basis continues to use the old version.
- Symptom: the model does not invoke the tool and directly gives an answer, and the return result contains values that do not exist in the business materials. Cause: the tool description or parameter descriptions are not clear enough, and the required parameters have no suitable values in the context.
Acceptance of this feature: run a test with a question missing required parameters, check the input parameters and return in the invocation record, and confirm whether it asks a follow-up question or invokes according to the description; at the same time, check whether the toolChoice and functionCall records are consistent with the three items of tool description, parameter descriptions, and whether required.