Document 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 |
|---|---|
| read_doc_contentsA | Read the contents of a document and return it as a string. |
| edit_documentA | Edit a document by replacing a string in the documents content with a new string. |
| return all the docsB | Return a list of all the document ids. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format_to_md | Rewrite the contents of a document in Markdown format. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: edit_document modifies content, read_doc_contents retrieves content, and return all the docs lists document IDs. There is no overlap in functionality, making tool selection unambiguous for an agent.
The naming is inconsistent with mixed conventions: edit_document uses snake_case with a verb_noun pattern, read_doc_contents uses snake_case but abbreviates 'document' inconsistently, and return all the docs uses a sentence-like format with spaces and no clear pattern. This lack of uniformity could confuse agents.
With only 3 tools, the set feels thin for a document management server, as it lacks operations like creating or deleting documents. While the tools cover basic read, list, and edit functions, the scope is limited and may require workarounds for full document lifecycle management.
There are significant gaps in the tool surface for document management: no create_document or delete_document tools, and missing operations like search or metadata updates. This incomplete coverage will likely cause agent failures when trying to perform common document workflows beyond reading, listing, and editing.