What this category’s data looks like
This category of data mainly comes from the national land and space planning one-map, project approval and supervision platform, current land use database, and ecological protection red line data. The update frequency is irregular. Daily associated documents include land pre-examination and site selection opinions, construction land planning permit, construction engineering planning permit, red line drawings, and planning conditions. Core fields cover project site selection scope, land scale, control boundary, and prior approval requirements. Corresponding units include spatial measurement units such as hectares and square meters, as well as identification fields like project number and approval document number.
What constraints these characteristics impose on tool calling and plugins
Data sources for this category are scattered, with no fixed update cycle. Tool calling requires configuring dynamic data pulling logic to avoid using expired planning control information. Daily associated documents have diverse formats, including vector drawings and approval texts. Plugins must adapt to multi-format parsing to accurately extract core fields such as site selection scope and land scale. Core fields involve spatial measurement units. Tool calling must unify unit conversion rules to prevent review deviations caused by unit mismatches. It is also necessary to connect to prior approval data from multiple departments. Plugins must comply with cross-platform interface calling specifications to ensure accurate data linkage.
Configuration guidelines
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Adapts to the multi-type consultation scenarios of this category, automatically matching tool calling logic |
| Single tool call timeout | 300 seconds | This category needs to pull data from multiple data sources, reserving sufficient interface response time |
| Tool result cache duration | 12 hours | Matches the irregular update rhythm of data in this category, avoiding the use of expired control information |
functionCall format verification | Enable strict mode | Core fields of this category require accurate extraction, and strict verification can avoid invalid format errors |
| Number of results returned by a single tool call | Top 10 | This category has a large number of core data entries, limiting the number of results can improve response efficiency |
| Plugin call data source scope | Only land and space planning and project approval data sources | Complies with the data control requirements of this category, preventing unauthorized access to irrelevant data |
Three common mistakes
- Tool call returns empty results. The cause is that access permissions for the corresponding data source are not configured, or the cache duration is set too long, resulting in use of expired data.
- Invalid JSON format error occurs, and the prompt contains Bad control character. The cause is that strict format verification for
functionCallis not enabled, causing invisible control characters to be mixed in during document parsing. - Tool call nodes cannot add connection lines. The cause is that interface plugin configuration binding is not completed, or there is a temporary abnormality in the node layout of the current version.
How to confirm the configuration is complete
- Initiate a test consultation involving land scale query, and check whether tool calling automatically triggers corresponding data source pulling.
- Submit a test request involving red line drawing parsing, and confirm that the returned results include accurate land scope fields.
- View tool call logs to confirm that format verification does not block valid requests, and there are no timeout errors.
- Test cross-data source calling, and confirm that the plugin only accesses authorized land and space planning-related data.
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.