This document applies to FastGPT v4.17.0.
What this category of data looks like
Data for this category primarily comes from VPC planning documents exported from cloud platform consoles, security group rule configurations, load balancer listener configurations, as well as external-provided network topology diagrams and traffic monitoring reports. Daily produced documents include network segment planning tables, access rule lists, health check configuration items, and change approval forms. Data updates are triggered with each network change. Fields include network segment masks, port ranges, protocol types, health check intervals, and there is no unified fixed cycle. Updates only occur in sync with business adjustments. Unlike cloud host delivery data, this category focuses on configuration details related to network connectivity and traffic distribution.
What constraints do these characteristics impose on the tool calling and plugin workflow
The data structure of this category has strong scenario specificity, and relies on native structured configuration fields of cloud platforms. Tool calling must adapt to non-general parameters such as network segment masks, port ranges, and health check intervals. Data updates are triggered by single network changes, with no fixed cycle. Tool calling must support real-time pulling of the latest configurations to avoid using expired historical data when generating test cases. Additionally, the defect analysis link requires association with traffic monitoring data. Tool calling must integrate multi-source data association query capabilities to ensure that test case coverage of configuration items matches actual deployment status. Errors in this category directly affect business access. Tool calling must include built-in configuration verification logic to proactively identify potential access failures or traffic forwarding errors.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Adapt to multi-parameter verification scenarios for cloud network configurations, automatically match available tools |
functionCall | ["describeVPCConfig", "listSecurityGroups", "checkLBListeners"] | Cover core VPC, security group, and load balancer configuration verification requirements for this category |
| Tool call timeout | 300 seconds | Cloud platform configuration pulling typically takes 100-200 seconds, reserves sufficient buffer for network requests |
| Tool result cache duration | 15 minutes | Cloud network changes occur infrequently, caching reduces repeated calls to cloud platform APIs |
| Maximum number of items returned per tool call | First 20 items | Aligns with default return item limits of cloud platform APIs, avoids result overload |
| Keywords that trigger tool calls | Load Balancer, Security Group, VPC, Network Topology | Match core business terms of this category to accurately trigger tool calls |
Three common mistakes
- Phenomenon: No return result after tool call execution, background shows call failure prompt. Cause: The tool list in the
functionCallparameter is not configured correctly, or the tool call switch is not enabled, preventing the large model from triggering the corresponding cloud network configuration pulling process. - Phenomenon: The generated test case contains the text "Reference Mark: [1]". Cause: The knowledge base associated document data returned by tool calling is not formatted and cleaned, and the original reference mark is directly appended to the output content.
- Phenomenon: After the user enters a specified keyword, the custom interface reply is not triggered, and the default answer is returned directly. Cause: The keyword-triggered tool call rule is not configured, or the custom interface call parameters are not bound to the tool calling workflow.
How to confirm the configuration is complete
- Initiate a test query containing "VPC configuration verification", check whether the corresponding tool call is automatically triggered, and verify whether the returned results include information such as VPC network segments and security group rules.
- View the tool call log, confirm that the value of the
toolChoiceparameter matches the configured setting, and that the tool call timeout setting does not trigger a timeout error. - Enter a query containing preset keywords, verify whether the custom interface or corresponding tool call workflow is triggered, and confirm that no default answer is returned.
- After generating the test case, check that the output content does not contain redundant reference mark text, confirming that the format cleaning rule has taken effect.
All configuration values listed above are common starting points. They should be evaluated against the reader's own specific samples and requirements.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.