What this category's data looks like
Data for this category primarily comes from daily production documents of skincare, haircare, makeup, and special cosmetics manufacturers. These documents include formula process sheets, weighing and feeding records, emulsification or filling records, cleaning and sanitization records, semi-finished and finished product inspection reports, and label review documents. Data sources cover registered or filed formulas, raw material safety materials, production equipment, ERP/MES systems, laboratory data, and packaging material version information. Update frequency is every production batch or each line change. Documents include fields such as raw material names, restricted substance content, production temperature, homogenization parameters, packaging batch numbers, and claim content. Some documents require exact matching of filed information fields.
What constraints these characteristics impose on the "tool calling and plugins" workflow
Data for this category updates per production batch or line change, and must strictly match registered or filed information. As a result, tool calling must support real-time pulling of the latest batch formulas, raw materials, and packaging data to avoid using expired documents. Documents contain precise raw material restricted substance content, production process parameters, label claim content, and other fields. Tool calling must verify that input parameters match filed fields to prevent parameter mismatches. Multi-source data comes from production equipment, ERP/MES, laboratory systems, and other sources. Tools must support connecting to different data sources and unifying data formats. Tools must also handle context retention when calls are interrupted, to ensure subsequent calls can resume unfinished verification tasks.
How to set up the configuration
These configurations are based on FastGPT v4.17.0:
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Adapts to process procedure Q&A scenarios, automatically triggers tool pulling of latest production data and filed information |
| Tool call timeout period | 300–600 seconds | Matches actual time taken for production data pulling and filing verification, prevents call failure due to delayed device responses |
| Context retention length | First 1000–1500 characters | Covers complete process parameters and filed fields for a single production batch, ensures full business data can be linked during Q&A |
| Single tool call limit | First 5 entries | Limits returned data volume to avoid exceeding context carrying capacity |
| Tool result verification switch | Enabled | Ensures raw material and packaging data returned by calls match registered and filed information, complies with category compliance requirements |
| Session resumption switch | Enabled | Supports resuming unfinished Q&A processes after tool call interruptions, avoids repeated verification requests |
Three common errors
- Symptom: Output interruption occurs during tool calling, with a "call timed out" prompt displayed on the interface. Cause: No timeout duration set adapted to production data pulling, causing device response delay to exceed preset thresholds and triggering interruptions.
- Symptom: Parameter missing error is returned when sending a termination command to an MCP server-side tool. Cause: Termination interface permission for the MCP service was not enabled in tool configuration, or call parameters did not match required fields for the MCP service.
- Symptom: No feedback is provided when calling external application startup functions. Cause: External application call permissions for the workflow were not configured, or the startup command’s path parameter did not match the actual installation path of the target program.
How to confirm the configuration is correct
- Initiate a Q&A request related to the process of a single production batch formula, check whether the data returned by tool calling matches the filed information for the current batch.
- Simulate a tool call interruption scenario, verify that session context is retained, and that unfinished Q&A processes can proceed normally after resumption.
- Send a termination command to the MCP server-side tool, verify that the server normally receives and executes the termination operation, with no parameter abnormality errors.
- Call the external application startup function, verify that the target program starts normally and can complete preset document operations.
The values provided are common starting points and should be measured against the reader's own samples.