What this category's data looks like
General mechanical equipment assembly business data typically comes from PLM, ERP, part inspection systems, assembly tool collection terminals, test benches, MES, and customer technical agreements. Daily generated documents include assembly process cards, multi-level BOMs, torque tightening records, gap adjustment records, commissioning reports, factory inspection sheets, packing lists, and more. Data is updated per device or per order. Fields include part numbers, torque values, gap parameters, concentricity readings, test results, and some data has clear units such as newton meters, millimeters, and megapascals.
What constraints these characteristics impose on tool calling and plugins
This category uses make-to-order assembly with multiple product varieties, so BOM levels are complex and adjust per order. Tool calling must support dynamic matching of exclusive data for the corresponding order. Data sources are scattered and include both structured and semi-structured content, so plugins must support multi-format document parsing. Each device’s inspection record must be bound to a unique order number, so tool calling must carry order identification parameters to avoid data confusion. Debugging data such as gap and concentricity values have precise units, so plugins must support validation and comparison of values with units to ensure the accuracy of inspection results. Additionally, assembly records must be updated in real time during production, so tool calling must support low-latency data pulling to avoid disrupting assembly cycle times.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Supports automatic selection of tools matching assembly inspection scenarios, no manual specification required |
| Workflow/API function-call configuration | enabled | Allows calling external tools to pull real-time assembly data and inspection records |
| Tool call timeout setting | 120–180 seconds | This category’s assembly inspection process typically includes multiple rounds of data validation, so the timeout setting must cover data pulling and comparison time |
| Plugin permission scope | Only allow access to PLM and MES data for the corresponding order | Prevents cross-order data leaks, aligns with data isolation requirements for make-to-order assembly |
| Context call count | Top 3 entries | Inspection for this category requires reference to latest process requirements, limiting context count reduces interference from redundant data |
| Number of plugins loaded simultaneously | No more than 5 | This category’s inspection tools are mostly dedicated data pulling tools, too many plugins will increase call latency |
This configuration example applies to FastGPT v4.17.0. All configuration values listed are common starting points, and should be validated against the user’s own samples.
Three common configuration errors
- API calls return permission denied errors. Symptoms include interfaces returning 403 status codes, or the interface displaying "no tool access permission". Causes: Access permissions for the corresponding tool are not configured in FastGPT, or order-level data isolation rules are not bound.
- MCP function integration fails in workflows. Symptoms include workflow node execution errors with prompts such as "plugin not found" or "data source format mismatch". Causes: The data source address for the MCP plugin is not correctly configured, or the format does not match the BOM and inspection record data for this category.
- Tool calling times out. Symptoms: Calls terminate after exceeding the set duration, and the interface displays a "call timed out" prompt. Causes: The timeout setting is not adjusted to match the duration required for this category’s assembly inspection process, or too many plugins are called simultaneously leading to excessive resource usage.
How to confirm configuration is complete
- Initiate a test call, enter a specified order number, and check if the returned results include BOM, torque records, and other data corresponding to that order, with no information from unrelated orders.
- Review tool call logs to confirm that
toolChoiceautomatically selects tools matching the current scenario,functionCallnormally triggers data pulling, and there are no failed call records. - Simulate a timeout scenario: set the call duration to a value smaller than the configured threshold to verify normal call completion; set the duration to a value larger than the configured threshold to verify that the call terminates after the set duration and displays a timeout prompt.
- Check plugin permission configurations to confirm that only system data for the current order is allowed to be accessed, with no logs of unauthorized access.