Data overview for this category
Data sources for this category include purchase orders, drawings and specification requirements, supplier quality certificates, data collected by inspection equipment, historical quality records, and supplier portal information. Updates occur when new inspection records are generated for each batch of incoming materials. Supplier rating updates are completed monthly or quarterly, with special audits conducted irregularly. Daily documents include inspection specifications, sampling plans, incoming material inspection reports, supplier audit reports, abnormal contact sheets, 8D rectification reports, and concession acceptance approval forms. Data fields include incoming material batch identifiers, actual number of sampled inspection pieces, non-conformity item types, rectification completion status, supplier rating levels, and other relevant fields.
Constraints on tool calling and plugin workflows
Data for this category is scattered across multiple processes including procurement, inspection, and supplier management. Tool calling must adapt to format differences across multiple data sources, and plugins compatible with different interfaces must be configured to pull required quality-related information. Data updates generate new records with each batch of incoming materials, so tool calling must support triggering execution by incoming material batch to avoid repeated processing of historical data. Daily document types are diverse and fields are inconsistent, so plugins must support parsing different document structures such as inspection reports and rectification reports, and accurately extract core fields including batch numbers and non-conformity items. Quality data is linked to production supply assurance and risk control, so tool calling must strictly match inspection batches and supplier information to prevent data misalignment that affects the accuracy of tender quotations.
Configuration settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Tool calling trigger mode | Trigger by incoming material batch | Matches the batch-based inspection update rhythm of this category |
| Number of entries returned per single call | Top 3 historical supplier data entries | Covers key reference basis for supplier quality |
| Plugin timeout period | 300–600 seconds | Adapts to time consumption requirements for multi-document parsing and cross-system data pulling |
| Workflow/API tool selection | auto | Allows the model to independently select appropriate tools to complete quotation preparation |
| Field extraction rule | Match the batch number field in the inspection report | Ensures data is bound to the corresponding incoming material batch |
| Number of failure retries | 2 times | Addresses temporary interface fluctuations and avoids terminating the process due to a single failed call |
Three common misconfigurations
- Symptom: An internal server error is returned in the interface when importing a custom plugin in a private deployment environment. Cause: The local execution permission of the plugin is not configured, or the environment variables did not correctly load the runtime environment dependent on the plugin.
- Symptom: When using an MCP tool encapsulated with the SSE protocol to initiate a call, the model prompts that the current connection method is not supported. Cause: The current FastGPT version only supports MCP plugins of the stdio process type, and does not support tool configurations using the SSE protocol.
- Symptom: After calling the HTTP component to obtain supplier quality data, the non-conformity item fields corresponding to the batch cannot be extracted. Cause: The field extraction rule does not match the actual field names in the inspection report, or the JSON structure returned by the interface is inconsistent with the preset extraction path.
How to confirm the configuration is correct
- Manually trigger a tool call by incoming material batch, and check whether the data source returned by the plugin includes the inspection data of the current batch.
- Check the plugin's log output to confirm that the protocol used during the call is stdio, and no error messages related to SSE appear.
- Verify the field extraction rule: input a simulated inspection report text, and confirm that the extracted fields match the preset rules.
- Confirm that the current FastGPT version is v4.17.0, which is compatible with the configured plugin type and calling logic.
Note: The configuration values listed above are common starting points, and should be evaluated against specific samples and use cases.