Docs MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docsA | |
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
With only one tool, there is no possibility of confusing tools with overlapping purposes. The single tool's purpose is clearly defined as searching documentation and returning relevant excerpts.
The tool name 'get_docs' follows a clear verb_noun convention. Since there's only one tool, naming consistency is trivially maintained.
A single tool feels thin for a general-purpose docs server, especially since only three libraries are explicitly supported. Borderline for a narrow utility, but it could benefit from additional operations like listing supported libraries or retrieving raw document content.
For the stated purpose—searching documentation for a query and library—the tool fully covers the operation. There are no obvious missing features within the described scope.