Skip to main content
Glama
Sign In
Office-MCP-Server

Office-MCP-Server

by stoyantsiparov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_accept_all_changes

Accept all tracked changes in a Word document, preserving insertions and removing deletions. Resolve revision marks to finalize the document.

Instructions

Accept all tracked changes in a Word document, keeping insertions and dropping deletions

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>"
    },
    "name": "word_accept_all_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the .docx file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the key behavioral nuance (insertions kept, deletions dropped) beyond what the name implies, giving the agent a concrete understanding of the modification semantics. It could mention in-place modification or return value, but the core behavior is well covered.

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 a single sentence of 15 words, front-loaded with the action, and every phrase adds value. There is no redundancy or filler.

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?

For a simple one-parameter tool with no output schema, the description is complete enough: it states the action, the resource, and the specific effect on tracked changes. Minor omissions like return value or explicit in-place save are not critical for a tool of this scope.

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?

The input schema has 100% coverage for file_path with a clear description, so the description adds no param detail. Baseline 3 is appropriate since the schema already fully documents the single parameter.

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 a specific verb ('Accept') and resource ('all tracked changes'), and clarifies the exact outcome: keeping insertions and dropping deletions. This distinguishes it from the sibling word_reject_all_changes and leaves no ambiguity about the tool's function.

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

Usage Guidelines4/5

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

The description clearly implies the tool's purpose and contrasts implicitly with word_reject_all_changes. It doesn't explicitly state exclusions or when-not-to-use, but the action is specific enough that usage context is clear.

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