An agentic RAG system with knowledge base search, document management, weather tools, and MCP integration for enterprise Q&A and operational analytics
Three tools with mixed quality. search_knowledge_base and list_knowledge_documents have detailed Chinese descriptions and clear purposes, but lack formal input schemas with type/description pairs in the source. get_current_weather has a minimal description ('工具:查天气' = 'Tool: check weather') and parameters with types but weak descriptions. No tools document output schemas. Error handling is present in implementation but not surfaced in tool definitions. No tool annotations (readOnlyHint, etc.) visible.
工具:查天气
列出知识库中已入库的全部文档清单(文件名、类型、切块数)。当用户询问知识库里有什么文档、有哪些资料、上传过什么文件时使用;不要用它检索文档内容。
在企业知识库(用户上传的PDF/Word/Excel文档)中检索与query相关的内容。凡涉及文档、标准、规范、条款、技术指标、试验方法、精密度、参数定义等问题必须先调用本工具,禁止凭模型记忆回答文档内容。query应为适合语义检索的自然语言问句。
get_current_weather has minimal description ('工具:查天气'). LLMs cannot determine when to use this tool vs alternatives or what it returns. Descriptions must be 50-200 chars and explain WHAT, WHEN, and WHAT IT RETURNS.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. search_knowledge_base returns formatted strings; list_knowledge_documents returns a summary; get_current_weather returns weather data. All three need explicit output schema documentation.
Parameter descriptions are weak or missing. 'extensions' in get_current_weather says 'optional, default base' but does not explain what 'base' vs 'all' means or when to use each. 'query' in search_knowledge_base lacks guidance on format or length.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | <=2025-11-25 | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. All three tools are read-only, but this is not declared in the tool definition. Agents cannot infer safety properties.
search_knowledge_base enforces a rate limit ('only 1 call per turn') but this constraint is buried in implementation logic, not documented in the tool description. Agents will not know this restriction exists.