What the data for this category looks like
The data for this category is primarily sourced from the national public resource trading platform, local trading platforms, project approval systems, and bidding supervision systems. The update frequency is daily. Daily processed documents include bidding announcements, qualification pre-qualification documents, bidding documents, tender documents, bid evaluation reports, public notices of successful candidates, and successful bid result announcements. Data fields focus on project qualifications, performance, bill of quantities, construction periods, and other content related to the bidding law framework. This category focuses on the full bidding process of construction projects, with clear scenario differences from government procurement data.
What constraints these characteristics impose on the "tool calling and plugins" link
Daily updated data sources require tool calling to adapt to the high-frequency synchronization rhythm. Set reasonable request intervals to avoid triggering platform rate limits. The structure of different types of bidding documents varies significantly. Plugins must support parsing text and structured data in multiple formats, adapting to different document types such as public information in bidding announcements and professional evaluation content in bid evaluation reports. Data fields focus on professional engineering content, so tool calling must match parsing rules for corresponding professional terms to ensure accurate extraction of information like qualifications and bill of quantities. Documents such as bid evaluation reports and objection complaints involve internal sensitive content. Tool calling must comply with internal office permission control requirements to prevent leakage of sensitive information.
How to set the configuration
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | Specify in the order of the tool list | Adapt to the sequential execution logic of tools in the bidding process, ensuring that links are triggered in the preset order |
functionCall | Enable forced call mode | Ensure the certainty of tool calling, avoiding the model from autonomously choosing to skip necessary business links |
| Tool call timeout | 600 seconds | Cover long-running business scenarios such as bid evaluation report parsing and bill of quantities comparison |
| Batch tool execution order | Execute in the order of workflow nodes | Match the sequential dependency relationship of the bidding process, ensuring that preceding links are completed before executing subsequent tools |
| Data source synchronization frequency | 2:00 AM daily | Match the daily update rhythm of the platform, avoiding high-frequency requests that trigger rate limits |
Reference only; verify against the target FastGPT release and deployment documentation.
Three Common Misconfigurations
- Some tools fail to run as expected, with only a subset of the configured tools in the workflow triggering. This occurs because the
functionCallforced call mode is not enabled, and the model autonomously skips some non-core tool calls. - The Playwright MCP service cannot be parsed, while the Amap MCP service runs normally. This is because the local network configuration of the Playwright service is not exposed to the FastGPT runtime environment, or the service port is not properly mapped.
- Streaming requests cause abnormal behavior in model nodes. This happens when the FastGPT agent streaming request configuration does not align with the Qwen3 model's non-streaming support requirements. Adjust the request mode to match the model's capabilities.
How to Confirm the Configuration Is Correct
- Trigger a test workflow, review the execution logs for each tool node, and confirm that all configured tools have call records.
- Import a standard bidding announcement document, and verify that the parsed results after tool calling match the document's content.
- Adjust the tool calling order, and confirm that the workflow execution sequence matches the configured node order.
- Check the data source synchronization logs to confirm that daily automatic synchronization tasks complete at the preset time.
The values provided here 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.