Skip to main content
Glama
Sign In
grp-docx-mcp

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

accept_change

Accept a tracked change in a Word document using its change ID: keep inserted text or remove deleted content.

Instructions

Accept a single tracked change by its change_id.

For insertions: keeps the inserted text (unwraps w:ins). For deletions: discards the deleted text (removes w:del).

Args: change_id: The integer id attribute of the w:ins or w:del element.

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": {
      "change_id": "<change_id>"
    },
    "name": "accept_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
change_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly explains the effect on insertions and deletions, but does not mention permissions, reversibility, or error conditions.

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 very concise: a two-sentence purpose statement followed by a bullet for the argument. Every sentence adds value, and the key information is front-loaded.

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

Completeness4/5

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

With one simple parameter and an output schema (not shown), the description covers the action and parameter semantics. It is adequate but could mention return type or error handling for full completeness.

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

Parameters5/5

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

The description adds significant meaning to the single parameter 'change_id', specifying it as 'The integer id attribute of the w:ins or w:del element'. This goes beyond the schema's 'Change Id' label.

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 uses the verb 'accept' with 'single tracked change' and specifies the behavior for insertions and deletions. It clearly distinguishes from siblings like accept_all_changes by focusing on a single change.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives (e.g., accept_all_changes or reject_change). It implies usage for a single change but lacks explicit guidance on prerequisites or exclusions.

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

Deploy Server

Other Tools