What data this category includes
The data for this category primarily comes from ERP material master data, melting furnace temperature measuring equipment, spectrum analyzers, MES production systems, mold management systems, and customer technical drawings. Daily retained documents include foundry process cards, alloy batching lists, heat run records, mold history logs, first article inspection records, material test reports, and nonconforming product review forms. Data updates occur per heat, per production batch, or daily. Core fields include heat number, alloy composition parameters, pouring temperature, mold cycle information, and return charge ratio parameters.
How these characteristics constrain tool calling and plugins
Multi-source heterogeneous data sources require configuring multiple cross-system plugins for tool calling. Each plugin must match the authentication and interface format of its corresponding data source. Frequently updated heat and batch data require binding tool trigger timing to production nodes to avoid redundant calls. The specific formats of core fields require adapting tool calling parameter validation rules to foundry industry-specific formats such as heat numbers and temperature parameters. The need to batch check alloy batching and trace defects to associated heats and mold cycles requires tools to support code running plugins for multi-data comparison and associated queries.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto or specified code running, web search plugins | Matches tool calling requirements for different quality traceability scenarios, such as using code running for batch batching comparison and web search for external standard queries |
| Workflow/API function-call configuration | Enabled | Forces the model to call tools in a structured format, ensuring that returned results can be parsed for defect traceability and data association |
| Tool call timeout | 120–180 seconds | Adapts to the average time interval for data return from equipment such as melting furnaces and spectrum analyzers, preventing single tool call timeouts from terminating the overall process |
| Number of returned entries per single tool call | Top 8 | Covers the core data volume associated with a single heat, including molds, batching, inspection, etc., avoiding redundant information interfering with analysis |
| Plugin authentication configuration | Preset parameters based on data source type | Matches interface authentication rules for different systems such as ERP, MES, and mold management systems, ensuring successful data pulling |
| Code running environment | Python 3.10 environment | Adapts to data analysis libraries commonly used for foundry industry data comparison, improving batch processing efficiency |
Three common mistakes
- Phenomenon: The tool call configuration interface cannot select code running plugins, and there is no wiring configuration area. Cause: Code running tool permissions are not enabled in system settings, or the current version does not adapt to the wiring logic of this plugin.
- Phenomenon: Empty results are returned after calling the web search plugin. Cause: Necessary parameters for the web plugin are not configured, or the search keywords do not match the format specifications of foundry industry quality traceability documents.
- Phenomenon: Fields returned by tool calls cannot associate heats with defect types. Cause: Parameter validation rules for tool calls are not configured for foundry industry-specific elements such as heat numbers and temperature parameters, resulting in incorrect data pulling formats.
How to confirm the configuration is complete
- Enter the tool call configuration interface and confirm that the
toolChoiceoption includes required plugins such as code running and web search. - Trigger a test call, enter a simulated heat number, and check whether associated data such as corresponding batching lists and heat run records can be pulled.
- View the tool call log to confirm that the returned result format of each plugin meets the preset foundry industry field requirements.
- In FastGPT v4.17.0, verify that the wiring configuration area of the code running plugin displays normally and can be dragged and connected to corresponding nodes.
The values provided are common starting points and should be measured against the reader's own samples.