What the Data for This Category Looks Like
Wind power yield-related data comes primarily from daily settlement data of regional power trading settlement platforms and wind farm operation and maintenance systems. Update full previous-day data on a T+1 daily basis. Do not acquire real-time unsettled current-day business data. Deliver data as structured JSON interface responses or CSV files. Include fields such as unique farm identification, statistical cycle, rated installed capacity, actual power generation, grid-connected settlement electricity price, fixed operation and maintenance allocated costs, and calculated revenue value. Use these units: actual power generation in megawatt-hours, grid-connected settlement electricity price in yuan per kilowatt-hour, and calculated revenue value in yuan.
Constraints Imposed on Tool Calling and Plugins
Wind power yield data is collected independently per farm. Include the unique farm identification as a filter parameter in all tool calls. Otherwise, returned data has no clear business purpose. Data uses T+1 settlement updates. Limit tool call query periods to settled historical dates. Queries for the current day or unsettled time periods return empty values or incorrect data. Specify required return fields explicitly to control data transfer volume and avoid invalid data occupying call resources. Most power trading data sources enforce call frequency limits. Configure tool call frequency thresholds to prevent triggering rate limiting rules.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
TOOL_CALL_ENABLE | Yes | This scenario requires calling external data interfaces to obtain wind power yield-related data, so enable the tool calling function |
tool_timeout | 30 seconds | Wind power trading data interface responses typically fall between 10-25 seconds. 30 seconds covers most normal call scenarios and avoids premature timeouts |
required_response_fields | Station Code, Statistical Date, Actual Power Generation, Grid Electricity Price, Accounting Revenue | Only return business-critical fields to reduce data transfer volume and lower parsing complexity |
api_auth_method | API_KEY | Most power trading data sources use API key authentication. Bind a dedicated key to obtain data access permissions |
rate_limit_per_minute | 10 calls | Public interfaces of regional power trading platforms typically limit calls to 15 times per minute. Setting 10 calls avoids triggering rate limits |
date_range_policy | Only query dates on T+2 or earlier | Wind power yield data updates on a T+1 basis. Queries for the current day or the previous day’s current time period return unsettled empty data |
tool_integration_protocol | REST_API | Most regional power trading platforms provide REST-style public interfaces. Self-developed plugins can select the MCP protocol as needed |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Mistakes
- Tool calls return the
The tool call is not supportederror. This occurs when the tool calling function is not enabled in the FastGPT application configuration, or tool calling permissions are not bound for the current model. - Calling the time plugin to retrieve statistical dates returns format errors or timeouts. This occurs when date format parameters are not specified as required by the data source, or a reasonable
tool_timeoutparameter is not configured. - Tool calls fail when calling local models in FastGPT version 4.8.19 and above. This occurs when model adaptation parameters for tool calling are changed in the new version, and the model's tool calling trigger configuration is not updated synchronously.
How to Confirm Proper Configuration
- Initiate a historical data query for a single farm in the FastGPT application debugging interface. Check if returned results include the preset
required_response_fieldsfields. - Review tool call logs. Confirm that the
rate_limit_per_minuteset rate limiting rule is not triggered, and that response durations do not exceed the configuredtool_timeoutvalue. - Attempt to query data for the current day. Confirm that returned results are empty or prompt that settlement is incomplete, aligning with the T+1 update business rule.
- Check the tool calling permission setting in the model configuration. Confirm that the current model supports tool calling functionality.
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-14.