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
Each tool handles a distinct operation: one reads document contents, the other edits by replacing a string. There is no overlap or ambiguity, so an agent can easily choose the correct tool based on the desired action.
Both tools follow a verb_noun pattern with snake_case (read_doc_contents, edit_document), which is consistent. However, one uses the abbreviation 'doc' while the other uses the full word 'document', creating a minor inconsistency in naming style.
With only two tools, the server feels very thin. The tools are fundamental but the count is borderline, offering minimal functionality for a document-focused server.
The set covers read and edit operations, but lacks create, delete, list, or search capabilities. These are notable gaps that could prevent agents from completing common document management workflows.