What the data for this category looks like
Data sources for this category include design BOM, silicon steel sheet and insulating material ledger, vacuum drying equipment logs, insulating oil test reports, partial discharge and withstand voltage test records, and product nameplate parameter tables. Data is updated per single product or each batch of raw materials. Documents include winding and assembly work orders, drying process records, insulation performance test sheets, and more. Core fields include insulation moisture content, partial discharge magnitude, and withstand voltage test voltage value, with corresponding units of ppm, pC, and kV.
What constraints do these characteristics impose on the tool calling and plugins workflow
The requirement for full-link data association for a single product means that tool calls must accurately bind multi-source documents such as the design BOM and test records of a single transformer, to avoid mixing data across batches. The unit and precision requirements for core detection fields require tools to automatically align field formats when calling external data interfaces. The high-frequency single-product update rhythm requires plugin configurations to adapt to short-cycle data pulling, while also verifying the integrity of core fields such as insulating oil moisture content and partial discharge values, to prevent analysis failure caused by missing key detection data.
How to set the configuration
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Allow the system to automatically match tool calls or directly generate analysis conclusions based on quality analysis queries |
| Workflow/API function-call configuration | Enable mandatory parameter validation | Ensure that only valid fields for a single product are passed when calling external interfaces, preventing cross-batch data from being mixed in |
| Tool call timeout period | 600 seconds | Adapt to long-cycle detection data pulling such as insulating oil tests and partial discharge tests that require waiting for equipment to return results |
| Number of results returned by a single tool call | Top 3 entries | Focus on core test records for a single product, reducing interference from irrelevant data on analysis |
| Plugin data format alignment | Calibrate based on actual measurements | Adapt to the units and precision of category-specific fields such as insulation moisture content (ppm), partial discharge magnitude (pC), and withstand voltage test voltage (kV) |
| Context binding rule | Single product ID | Ensure all tool calls only associate data for the single transformer currently being queried, avoiding mixing data from multiple products |
Three common errors
- Phenomenon: An AggregateError Code: ETIMEDOUT is returned when calling a plugin via custom code. Cause: The pull duration for long-cycle detection data such as insulating oil tests and partial discharge tests is not adapted, and the default timeout setting is too short, causing the request to be interrupted.
- Phenomenon: The test data returned by tool calls does not match the current product, and cross-batch records appear. Cause: The context rule for binding a single product ID is not configured, causing detection data from other batches to be mixed in during calls.
- Phenomenon: Core fields such as partial discharge magnitude are empty, and the analysis result has no valid reference. Cause: The field integrity check of the plugin is not enabled, and records with missing key detection data are not filtered out.
How to confirm the configuration is complete
- Use the FastGPT v4.17.0 platform interface to initiate a quality traceability query for a single transformer, and verify that tool calls only return test records and assembly documents for that product.
- Simulate long-cycle data pulling to confirm that the tool call timeout period matches the category's detection data return rhythm.
- Trigger a plugin call and check whether the field units and category-specific parameters of the returned data are aligned.
- View the tool call log to confirm that only valid parameters for the current product are passed in
functionCallmode, with no redundant fields.
The values provided here are common starting points and should be evaluated against the reader's own samples.