McpDocServer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment setting for Node.js application | development |
| PUPPETEER_SKIP_DOWNLOAD | No | If set to 'true', puppeteer will use the locally installed Chrome browser instead of downloading its own version. | true |
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 |
|---|---|
| docs_search_docsD | – |
| docs_get_doc_detailD | – |
| docs_list_docsD | – |
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 3 tools
The three tools have clearly distinct purposes: get_doc_detail retrieves a specific document, list_docs enumerates documents, and search_docs finds documents based on criteria. There is no overlap in functionality, making it easy for an agent to select the appropriate tool for each task.
All tool names follow a consistent snake_case pattern with a 'docs_' prefix and a clear verb_noun structure (get_doc_detail, list_docs, search_docs). This uniformity aids in predictability and readability across the tool set.
With three tools, the server is well-scoped for basic document operations, but it feels slightly thin as it lacks update or delete capabilities. However, for a minimal document server, the count is reasonable and each tool serves a distinct purpose.
The tool set covers core read operations (get, list, search) but lacks update, delete, or create functionalities, which are typical for a document management domain. This creates notable gaps that agents might need to work around, though the existing tools provide a functional baseline.