Word MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTPUT_DIR | No | The directory where generated Word documents will be saved | ./output |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_reportC | Generates a complete Word document based on a structured content payload. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined and distinct by default.
Since there is only a single tool, naming consistency is inherently perfect—there are no other tool names to be inconsistent with. The tool name 'generate_report' follows a clear verb_noun pattern.
A single tool is too few for a server named 'Word MCP', which implies broader document manipulation capabilities beyond just report generation. This minimal toolset feels thin and under-scoped for the apparent domain.
The tool surface is severely incomplete for a Word document server; it only covers report generation, missing essential operations like document editing, formatting, saving, or loading. This will likely cause agent failures when broader document tasks are needed.