docs-rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search the documentation corpus with TF-IDF retrieval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between overlapping tools. The purpose of search_docs is singular and clear.
The single tool name 'search_docs' follows a clear verb_noun pattern, which is consistent for the server's scope. There are no other names to compare, so it is perfectly consistent.
A single tool for a docs RAG server is borderline but acceptable, as search is the primary function. However, it feels slightly thin, and additional tools like list_docs or get_doc could enhance usability.
For a documentation search server, search_docs covers the core retrieval need. Minor gaps exist such as no ability to list available document sources or fetch a specific document directly, but these are not critical for basic RAG workflows.