MCP Chat
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 |
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 completely distinct: one reads document contents, the other edits them. There is no overlap or ambiguity in their purposes.
Both names follow a verb_noun pattern, but one uses the abbreviation 'doc' while the other uses 'document', and one refers to 'contents' while the other uses 'document'. Minor inconsistency, but the pattern is still readable and predictable.
With only two tools, the server feels thin for a document-related service. While each tool has a clear purpose, the low count is borderline for being considered a well-scoped set.
The server supports reading and editing but lacks create, delete, or listing capabilities. Editing is limited to string replacement, which restricts the possible workflows agents can perform.