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_docB | Read the contents of a document. |
| edit_docB | Edit the contents of a document by replacing the old content with new content. |
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
read_doc and edit_doc have clearly distinct purposes: one retrieves contentaren't and the other modifies it. There is no overlap or ambiguity between the two tools.
Both tools follow the same verb_noun snake_case pattern: read_doc and edit_doc. The naming convention is perfectly consistent across the set.
With only two tools, the server feels minimal and borderline thin for most use cases. However, for a narrowly scoped document read/edit utility, the count is not unreasonable.
The tool surface covers reading and editing but lacks create, delete, list, or search operations, preventing any real document lifecycle management. Agents cannot discover or create documents, which creates significant workflow gaps.