Documents-MCP-Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
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 |
|---|---|
| read_doc_contentsB | Read the contents of a document and return it as a string. |
| edit_doc_contentsB | Edit the contents of a document and return the updated content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format | Rewrite the contents of a document in a markdown format. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: read_doc_contents retrieves content, while edit_doc_contents modifies it. There is no overlap or ambiguity in their intended use.
Both tools follow a consistent verb_noun pattern (read_doc_contents, edit_doc_contents), with the same object name 'doc_contents' and clear action verbs. The naming is predictable and readable.
Two tools is borderline thin for a document management server. While each tool earns its place, the set lacks basic operations like create, delete, or list, making the surface feel incomplete rather than well-scoped.
The server only supports reading and editing existing documents. It is missing create, delete, and list/search operations, which are fundamental for a documents domain and will cause agent failures when trying to manage documents beyond read/edit.