MCP server exposing RAG tools for querying knowledge bases, managing documents, and configuring retrieval settings
Server has 16 tools with complete input schemas and basic descriptions. Naming follows verb_noun convention (rag_query, list_knowledge_bases, create_knowledge_base, delete_document). However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs. alternatives. Parameter descriptions exist but are minimal (avg ~40 chars). No output schemas documented. Error handling and recovery guidance absent. Missing tool annotations (readOnlyHint, destructiveHint). Composition is reasonable, tools are single-purpose, but chaining guidance is absent.
Clear retrieval settings for a knowledge base (revert to defaults).
Create a new knowledge base.
Create a presigned URL for direct file upload.
Delete a document from a knowledge base.
Delete a knowledge base (soft delete).
Get effective retrieval settings for a knowledge base (merged with app defaults).
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., does rag_query return source_ids for follow-up retrieval?). Violates pattern:tool and pattern:response-shaper.
Descriptions lack LLM-optimized guidance. Generic descriptions like 'Query the RAG backend and return answer with sources' do not explain WHEN to use rag_query vs. retrieve_chunks, or what 'sources' means. Violates pattern:tool-description.
Missing tool annotations. Destructive tools (delete_knowledge_base, delete_document) lack destructiveHint. Read-only tools (list_*, get_*) lack readOnlyHint. Prevents LLM from reasoning about safety and retry logic.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Get retrieval settings for a knowledge base.
Ingest plain text content into a knowledge base.
Ingest content from a URL into a knowledge base.
List documents for a knowledge base.
List knowledge bases in the backend.
Query the RAG backend and return answer with sources.
Retrieve relevant chunks without generating an answer.
Set retrieval settings for a knowledge base.
Update knowledge base settings.
Upload a document file to a knowledge base.
No error handling or recovery guidance. Tools do not document what errors are retryable, user-fixable, or fatal. No guidance on 'knowledge_base_id not found, call list_knowledge_bases() first.' Violates pattern:recovery-guide.
Parameter descriptions are minimal (~40 chars avg). 'Optional knowledge base ID (uses default if not provided)' lacks detail on what 'default' means or how to discover available IDs. Violates pattern:tool-description baseline of 72+ chars per param.