MCP Docs 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsC | Search through all documentation files for a given query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api/resources | Documentation for resources in api category |
| api/tools | Documentation for tools in api category |
| examples/basic-usage | Documentation for basic-usage in examples category |
| getting-started/installation | Documentation for installation in getting-started category |
| getting-started/introduction | Documentation for introduction in getting-started category |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_docs' has a clear and distinct purpose that cannot be confused with any other tool in the set.
The single tool follows a consistent verb_noun pattern with 'search_docs'. Since there is only one tool, the naming is inherently consistent with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'MCP Docs Server', which suggests a documentation-focused domain. This minimal set lacks basic operations like retrieving, creating, updating, or deleting documents, making it feel thin and incomplete for the apparent scope.
The tool set is severely incomplete for a documentation server. While 'search_docs' provides a useful function, there are obvious gaps such as no CRUD operations (e.g., get_doc, create_doc, update_doc, delete_doc) or other lifecycle management tools, which will likely cause agent failures in handling documentation tasks.