What Data for This Category Looks Like
Data sources for survey and design mainly include point coordinates collected by on-site survey equipment, load parameters generated by structural calculations, progress ledgers exported from project management systems, structured survey reports, and unstructured CAD drawings and PDF design documents. Data update frequency varies with project phases: updated per single survey task or daily during on-site survey stages, and updated with drawing version iterations during construction drawing design stages. The length of individual documents varies widely, ranging from ledger entries of a few hundred characters to complete design descriptions of tens of thousands of characters. Core fields include project number, survey point coordinates (unit: meters/longitude and latitude), drawing version number, load parameters (unit: kilopascals), and progress nodes (unit: days).
Constraints Imposed on Tool Calling and Plugins
The data characteristics of survey and design impose multiple constraints on the tool calling and plugins workflow. First, data sources include structured ledgers and unstructured CAD and PDF documents. Tool calling nodes must support both structured data reading and unstructured file parsing, and must adapt to parsing plugins for industry-specific file formats. Second, data update frequency changes dynamically with project phases. Tool calling data source binding must support dynamic switching based on project nodes, to avoid calling outdated survey or design data. Third, core fields include multiple unit types. The parameter verification link of tool calling must support automatic unit identification and verification, to prevent passing mismatched parameter values. Fourth, the length of individual documents varies widely. The context carrying capacity of tool calling must support dynamic adjustment of thresholds, to avoid information loss caused by truncation of overly long content.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Adapts to tool calling priority in survey and design scenarios, automatically matches structured data reading or unstructured file parsing tools |
functionCall | enabled | Enables function calling capabilities for structured data, supports reading structured fields such as project ledgers and load parameters |
| Tool calling timeout | 300–600 seconds | Parsing survey and design files usually takes a long time, sufficient time must be reserved to complete CAD or PDF document parsing |
| Unstructured file parsing plugin | Calibrated based on actual testing | Must adapt to industry-specific CAD and PDF formats, parsing effects vary across different plugins |
| Tool result unit verification | Enabled | Core fields of survey and design include multiple unit types, automatic verification is required to ensure parameter units match business requirements |
Three Common Misconfigurations
- Symptom: Tool calling fails when calling a locally deployed large model, with logs showing the model does not support function calling format. Cause: Failed to confirm whether the locally deployed large model is compatible with the
functionCallformat. Some open-source models require enabling a dedicated tool calling branch. - Symptom: Request timeouts or duplicate results occur during concurrent calls, with status code 429 returned. Cause: Failed to adjust the concurrency upper limit configuration of the tool calling node, and failed to set a reasonable concurrency threshold for the time-consuming large file parsing of survey and design.
- Symptom: Tool calling results are unstable, with incorrect units or empty fields for extracted load parameters. Cause: Failed to enable the tool result unit verification configuration, and failed to set post-processing logic for multi-unit fields in survey and design.
How to Confirm Successful Configuration
- Submit a test request that includes a survey point coordinate query, and verify whether the fields returned by the tool call include the project number and point coordinates.
- Upload a test CAD design drawing, and confirm that the tool calling node can successfully parse and extract the drawing version number and load parameters.
- Adjust the tool calling timeout configuration, submit multiple large file parsing requests, and confirm that no persistent timeout errors occur.
- Enable the tool result verification function, pass test parameters with incorrect units, and confirm that the system triggers a unit mismatch prompt.
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.