What this category of data looks like
New energy development policy and regulatory basis data is primarily sourced from official announcements, industry standard documents, and local implementation rules issued by the National Energy Administration and provincial energy authorities. The knowledge base syncs within 1 to 3 days after a major policy release. Routine policies are updated monthly. Document structure includes fields such as document number, issuing authority, effective date, applicable scenario, clause content, and attachment materials. Unique fields include project filing number, grid connection acceptance standard, and carbon emission reduction accounting indicators. The length of individual documents mostly falls between 1000 and 5000 characters.
What constraints these characteristics impose on tool calling and plugins
Long new energy policy documents with nested clauses require tool calling context windows to support long text parsing. Frequent policy updates require tool calling to support dynamic switching of knowledge bases or real-time synchronization of the latest policy data. The presence of unique fields requires tool calling retrieval parameters to precisely match field names, to avoid result deviations from generalized retrieval. Regional policy differences require tool calling to support dynamic selection of regional policy knowledge bases based on input parameters, to improve retrieval accuracy.
How to configure settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Supports multi-clause retrieval needs for new energy policies, automatically selects appropriate tool calling strategies |
| Knowledge base variable reference | Knowledge base ID passed via workflow input | Supports retrieval needs for different regional new energy policies, enables dynamic knowledge base switching |
| Tool calling timeout duration | 600 seconds | New energy policy documents are lengthy, requiring longer response times for retrieval and parsing |
| Context window size | 8000–12000 token | Matches the length of new energy policy documents, prevents truncation of critical clauses |
| Tool calling retry count | 2 times | Addresses temporary retrieval failures caused by delays in knowledge base synchronization |
Three common errors
- Symptom: Tool calling nodes repeat execution, with logs showing multiple identical retrieval requests being triggered. Cause: No clear execution branch termination logic is configured after the tool calling node, causing the workflow to trigger repeatedly in a loop.
- Symptom: Retrieval results are empty when passing knowledge base variables via the API. Cause: The matching rules for variable format and knowledge base ID are not verified, causing the referenced knowledge base to not exist or have an incorrect format.
- Symptom: Returned policy clauses from tool calling are incomplete. Cause: The context window is set too small, truncating lengthy clause content and causing loss of critical policy information.
How to verify proper configuration
- Manually trigger the workflow, pass the specified regional new energy policy knowledge base ID, and check if retrieval results match the corresponding regional policy documents.
- View workflow logs to confirm that the
toolChoiceparameter value matches the configured setting, with no abnormal error messages. - Simulate an API call to pass the knowledge base variable, and check if the workflow can correctly receive and use the variable for retrieval.
- Test retrieval of a lengthy policy document, and confirm that returned content is not truncated and covers complete clause content.
The values provided here are common starting points, and should be evaluated 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.