What the data for this category looks like
Coal transportation and sales business data mainly comes from internal transportation and sales scheduling systems, weighbridge metering systems, and railway/port shipment ledgers. The core unit is single batch waybills, updated according to the waybill generation rhythm, and archived after single-waybill settlement is completed. Each data document includes fixed fields such as coal type, shipment volume (unit: ton), shipment time, consignee, carrier, freight unit price (unit: yuan/ton), and settlement status. Some cross-region waybills also include transfer node information. The data structure is relatively standardized, but the fields are highly specialized.
Constraints on tool calling and plugins workflow
Specialized fields for coal transportation and sales require tool calls to exactly match exclusive field names, to avoid data deviation caused by generic extraction. Frequently updated waybill data requires plugins to set reasonable refresh frequencies, balancing real-time performance and system resource consumption. Multiple system data sources require plugins to be configured with cross-system connection parameters, to ensure simultaneous pulling of weighbridge metering and shipment ledger data. Additionally, users often need line charts to display shipment volume trends. This requires chart data returned by tools to follow standardized structured formats, otherwise it cannot be rendered normally in the chat interface.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
toolChoice | auto | Adapts to the multi-tool parallel call business scenario of coal transportation and sales, automatically matches corresponding tools to handle waybill query, data statistics and other needs |
| Tool call timeout | 300 seconds | Cross-system data pulling for coal transportation and sales usually requires a certain response time, preventing tool call processes from being interrupted due to timeout |
| Maximum returned results | Top 20 entries | Controls the volume of waybill data returned by a single tool call, avoiding context overload that affects model understanding |
| Plugin data refresh frequency | Every 15 minutes | Matches the daily waybill update rhythm, balancing data real-time performance and server resource consumption |
functionCall | enabled | Enforces structured tool calls, ensuring the model generates compliant call instructions and adapting to the precise extraction needs of coal transportation and sales data |
| Chart rendering format | JSON structured data | Follows the line chart rendering specifications of the FastGPT chat interface, and must include key-value pair structures for x-axis time and y-axis values |
Three Common Configuration Mistakes
- Phenomenon: After calling an MCP tool to return a line chart, it cannot be displayed in the chat interface. Cause: The returned line chart data does not include the standard key-value pairs for x-axis time and y-axis values, which does not meet FastGPT's rendering requirements.
- Phenomenon: The interface displays the
Your model may not support tool_call SyntaxErrorerror. Cause: ThefunctionCallortoolChoiceparameters are not configured correctly, causing the model to fail to recognize valid tool call syntax. - Phenomenon: The waybill data returned by the tool call lacks core fields such as coal type and shipment volume. Cause: The exclusive coal transportation and sales fields to be pulled are not specified in the plugin configuration, resulting in incomplete data extraction scope.
How to Confirm Configuration is Correct
- Initiate a test query including "query recent coal shipment volumes", check whether the system triggers tool calls and returns corresponding waybill data.
- Import preset coal shipment volume line chart test data, confirm that the chat interface can normally render the visual chart.
- Check the FastGPT backend logs, confirm there are no prompts for tool call syntax errors, verify that the
toolChoiceandfunctionCallparameter configurations take effect. - Wait for the plugin refresh cycle to end, check whether the data is updated at the preset frequency, confirm that the cross-system pulling logic is working properly.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.