What data for this category looks like
Data sources for this category include purchase orders, drawing specifications, supplier quality certificates, inspection equipment logs, historical quality ledgers, and supplier portal documents. Daily generated documents include inspection specifications, sampling plans, incoming material reports, supplier audit reports, exception contact sheets, 8D reports, and concession acceptance approval forms. Corresponding reports are generated with each batch of incoming materials as part of data updates. Supplier quality evaluations are completed monthly or quarterly, and audits are conducted irregularly to update records. Documents include fields such as batch number, inspection parameters, qualified judgment results, and supplier codes. Some documents are associated with drawing versions and sampling standard numbers.
Constraints imposed by these characteristics on tool calling and plugins
Data sources are scattered and updates have no fixed cycle. Tool calling must support synchronized pulling from multiple data sources to avoid review deviations caused by delayed data source updates. Document types are diverse and have large field differences. Parsing rules adapted to different document structures must be configured to ensure the accuracy of cross-document field association. Documents associated with incoming material batches must be bound to unique batch identifiers. Tool calling must pass batch parameters to filter corresponding data and prevent cross-batch data confusion. Supplier quality data must be associated with historical exception records. Tool calling must support cross-knowledge base associated queries to ensure the completeness of root cause analysis.
Configuration settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Supports automatic function calls for multiple document types such as inspection reports and 8D reports, no need to manually specify the call target |
| Document chunking rule | Differentiate by document type: 500–800 characters for inspection reports, chunk 8D reports by chapter | Matches the structural characteristics of different documents, ensuring contextual integrity for cross-document field association |
| Single search limit | Top 10 results | Covers multi-dimensional data such as associated suppliers, historical quality records, and incoming material batches for this category, avoiding information omission |
| Workflow/API function-call configuration | Enable required field verification | Ensures core fields such as batch number and supplier code are passed when calling tools, preventing invalid reviews |
| Context window limit | 8000 token | Covers the full review requirements of associated documents including drawing specifications, historical exception records, and current incoming material reports |
| Data source synchronization frequency | Calibrated based on actual testing | Adapts to non-fixed update rhythms such as per-batch incoming materials and quarterly evaluations, avoiding expired or redundant data |
Three common configuration mistakes
- A "missing required field" error is returned when calling tools. This occurs when required field verification is not enabled in the
functionCallconfiguration, and batch numbers or supplier codes are not required to be passed. - After the workflow calls the API to upload files, the uploaded files cannot be associated with the corresponding knowledge base. This occurs when the knowledge base ID is not configured as a global variable, or the format of the passed parameters does not meet system requirements.
- The number of search results does not match expectations. This occurs when the single search limit is set too low, failing to cover the retrieval requirements of multi-dimensional associated data.
How to verify a correct configuration
- A standard incoming material report and the corresponding supplier quality certificate are uploaded, tool calling is triggered, and whether the returned results include core fields such as batch number and inspection parameters is checked.
- The workflow API is called to upload documents, and whether the target knowledge base ID and global variable parameters are correctly associated in the system logs is verified.
- Cross-document associated queries are simulated to verify that historical 8D reports and exception records of the corresponding supplier can be retrieved.
- Tool calling is manually triggered in the debugging interface of FastGPT v4.17.0, and whether the function automatically matched by
toolChoicematches the current review task type is confirmed.
The values provided here are common starting points and should be measured against the reader's own samples.