What data for this category looks like
Data sources for this category include purchase orders, drawings and specifications, supplier quality certificates, inspection equipment data, historical quality records, and supplier portals. Update cycles cover immediate verification for each batch of incoming materials, monthly or quarterly supplier evaluations, and ad-hoc special audits. Daily processed documents include inspection specifications, sampling plans, incoming material reports, supplier audit reports, abnormality contact sheets, 8D rectification records, and concession acceptance approval forms. Data fields include incoming material batch number, sampling sample size, inspection item name, non-conforming item category, full supplier name, and rectification measure records, which need to adapt to the native field formats of different documents.
What constraints these characteristics impose on the "tool calling and plugins" workflow
Dispersed data sources and varied formats require tool calling to support cross-source data retrieval, and adapt to multiple data formats such as PDF, Excel, and structured interfaces. High-frequency update demands that tool calling supports batch triggering and fast response, to avoid blocking production processes. Large differences in field structures across different documents require plugins to have flexible field extraction and mapping capabilities, ensuring that the fields of process documents and abnormal reports match business requirements. At the same time, errors directly affect production stability, so failure retry and data verification mechanisms must be configured to avoid the risk of defective materials entering production or incorrect rejection.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | Set to auto | Adapt to multi-tool automatic selection scenarios, matching the need for incoming material inspection to call multiple data sources such as purchase orders and supplier quality certificates |
| Single tool call timeout | 600 seconds | Adapt to the reading and parsing duration of a single 8D rectification report or large inspection specification, to avoid process blocking |
| Plugin call retry times | 3 times | Respond to temporary fluctuations in supplier portal interfaces or network jitter scenarios, improving call success rates |
| Batch processing batch upper limit | First 10 batches | Match the processing rhythm of each batch of incoming materials, avoiding process interruption due to exceeding system resource thresholds |
| Context retention length | 800–1200 characters | Adapt to the core field extraction requirements of documents such as inspection specifications and sampling plans, avoiding redundant information interfering with large model generation |
| Workflow/API function-call configuration | Enable mandatory format verification | Ensure that non-conforming item data returned by tools conforms to preset field formats, reducing format errors in abnormal report drafting |
Three common mistakes
- Phenomenon: Supplier portal plugin calls return empty fields. Cause: Pre-extraction steps for supplier codes are not configured, resulting in missing plugin call parameters and inability to locate target supplier data.
- Phenomenon: Tool calls time out, and the interface returns status code 504. Cause: The set single call timeout duration is too short, not adapting to the reading and parsing process of large 8D reports, resulting in timeout triggered before data retrieval is completed.
- Phenomenon: Non-conforming judgments returned by tools are not associated with historical quality data, leading to misjudgments in abnormal reports. Cause: Mandatory format verification for
functionCallis not enabled, and the association step for calling historical quality data plugins is not configured. Judgments are generated directly based on the inspection results of the current batch only, without reference to past supplier quality records.
How to confirm the configuration is complete
- In FastGPT v4.17.0, upload a standard incoming material inspection specification PDF, trigger the file reading plugin, and verify that the extracted inspection items match the preset fields in the document.
- Call the supplier portal plugin, enter the preset supplier code, and verify that the returned quality certificate fields conform to the required business format.
- Simulate the abnormal scenario of a single batch of incoming materials, trigger the tool call process, and verify that the result is only passed to the large model as context and not directly output to the front-end interface.
- Configure batch triggering rules, submit 2 batches of incoming material data, and verify that tool calls are executed in batch order without timeout errors.
The values provided are common starting points and should be measured against the reader's own samples.