MCP Chat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API secret key |
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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format | Rewrites the contents of the document in Markdown format. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one reads document contents, the other modifies them. There is no overlap or ambiguity between the operations.
Both tools use a verb_noun pattern and snake_case, but one uses 'doc_contents' and the other uses 'document', which is a minor inconsistency. A more consistent pair would be read_document/edit_document.
Two tools is a thin surface and falls at the borderline for a useful server. The tools are focused, but the count feels minimal for a standalone document-related MCP server.
The tool surface covers reading and editing documents but lacks create, delete, list, and search capabilities. This leaves significant lifecycle gaps that agents may need to work around.