docx-mcp-server

Overview Schema Source Related Servers Discussions Admin

add_comment

Add a comment to specific text in a Word document. Attach comments to the first occurrence of chosen anchor text with author and content.

Instructions

Add a comment to specific text in the document. The comment is anchored to the first occurrence of the anchor text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>",
      "anchor_text": "<anchor_text>",
      "comment_text": "<comment_text>"
    },
    "name": "add_comment"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Absolute path to the .docx file
`anchor_text`	Yes	Text to attach the comment to (must exist in the document)
`comment_text`	Yes	The comment content
`author`	No	Comment author name	Claude

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0May 29, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description bears full burden for behavioral disclosure. It reveals one key behavior (anchoring to first occurrence) but omits others such as mutability, error handling (if anchor not found), and whether comments are inline or separate. This is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences with no redundant words. The core action and unique behavior are front-loaded in the first sentence, making it immediately clear. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no output schema, and no annotations, the description covers the basic purpose but lacks completeness about return values, error scenarios, and prerequisites. A sentence about what the tool returns or what happens if anchor_text lacks would make it more complete. As is, it is minimally viable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description is not required to explain parameters. It adds minimal extra context about 'anchoring' which relates to anchor_text, but the schema already describes anchor_text as 'Text to attach the comment to'. Thus, the description provides no significant added meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Add a comment') and the specific target ('to specific text in the document'), and includes a unique behavior ('anchored to the first occurrence of the anchor text'). This distinguishes it from siblings like 'add_comments' and 'reply_to_comment', which may have different anchoring or scoping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'add_comments' (plural) or 'reply_to_comment'. There is no mention of prerequisites (e.g., document must exist) or scenarios where this tool is inappropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.