This document is written based on FastGPT v4.17.0.
What This Category of Data Looks Like
Data for this category comes from design BOM, silicon steel sheet and insulating material inventory data, vacuum and drying equipment operation logs, oil test reports, and high-voltage test records from test stations. Data update rhythm is once per product, with synchronized updates per batch of raw materials. Daily documents include winding and core assembly records, vacuum drying records, insulating oil reports, partial discharge and withstand voltage test reports, and nameplate parameter tables. Fields include rated voltage (unit: kilovolts), insulation resistance (unit: megohms), partial discharge value (unit: picocoulombs), test date, batch number, nameplate number, and more. Single-product inspection records must be bound to the exclusive BOM for traceability.
Constraints Imposed on Tool Calling and Plugins Workflow
Single exclusive inspection records require tool calls to precisely match the single product’s ID and batch information, to avoid cross-batch data confusion. Multiple types of structured documents require plugins to adapt to extraction of different formats of test reports and BOM data, and cannot rely on unified text chunking rules. High-frequency single-product data updates require tool calls to support real-time pulling of the latest test data from test stations. Strict requirements for core inspection indicators mean that tool call return results must undergo field integrity checks, to prevent audit errors caused by missing key parameters. The single-product traceability business logic requires context binding to be limited to the full set of inspection records for a single product, to avoid mixing data from other products. Dynamic judgment of whether to call tools can be achieved by configuring toolChoice as auto, to adapt to different inspection and audit scenarios.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Adapt to the dynamic tool calling needs of inspection and audit scenarios, automatically judge whether to retrieve test data or knowledge base content |
| Workflow/API function-call configuration | enabled | Structurally extract core fields from insulating oil reports and test reports, ensure return results comply with audit logic |
| Tool call timeout | 120 seconds | Match the network latency range for test data retrieval, avoid call interruptions caused by large data volumes |
| Maximum number of single tool calls | first 3 | Cover the field extraction needs of the main inspection documents for a single product, avoid timeouts caused by excessive calls |
| Context binding dimension | Bind full historical records of a single product | Comply with the single-product traceability business requirements of this category, prevent cross-batch data from interfering with audit results |
| Global variable passing method | Pass via system global variable node | Stably pass global parameters such as batch number and test station ID, ensure precise matching of tool calls |
Three Common Misconfigurations
- Symptom: Tool call returns include irrelevant zero fields. Cause: Single product context was not correctly bound, leading to redundant data from other batches being included in the call.
- Symptom: Plugin display name differs between the system plugin list and plugin management page. Cause: Internal identifier and front-end display name were not filled in synchronously in plugin configuration, leading to misalignment between internal naming and front-end display.
- Symptom: Tool calls do not retrieve insulating oil report data from the knowledge base, only generating generic responses. Cause: Association trigger conditions between tool calls and the knowledge base were not configured, and the target knowledge base scope was not specified.
How to Verify Correct Configuration
- Initiate an inspection and audit request for a single transformer, check the tool call logs in the session details to confirm the trigger timing matches the preset single product ID rules.
- Enter the plugin management page, verify that the front-end display name of the plugin matches the system internal identifier, confirm that the name synchronization configuration is complete.
- Retrieve the insulating oil report knowledge base entry for the corresponding product, verify that tool calls can pull structured fields such as insulation resistance and partial discharge value.
- Initiate a test after configuring global variable parameters, check the parameter details of the tool call request to confirm that global variables were passed correctly.
The values provided here are common starting points and should be measured against the reader's own samples.