MCP Chat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | 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_documentB | Edit the content of a document by replacing a string in the content with a new string |
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 2 tools
The two tools have clearly distinct purposes: one reads document contents, the other edits them. There is no ambiguity or overlap between them.
Both tools follow a verb_noun pattern, but the nouns differ slightly ('doc_contents' vs 'document'). This is a minor inconsistency that does not significantly harm readability.
With only two tools, the server feels thin, but for a narrow document manipulation purpose it is not unreasonable. It is borderline and lacks the richness of a more complete toolkit.
The domain appears to be document manipulation, but read and edit are the only operations available. There is no create, delete, or list functionality, leading to significant gaps in basic lifecycle coverage.