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

Office-MCP-Server

by stoyantsiparov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_reject_all_changes

Reject all tracked changes in a Word document, restoring deletions and removing insertions to finalize the content.

Instructions

Reject all tracked changes in a Word document, restoring deletions and dropping insertions

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_reject_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/5.0
Behavior3/5

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

No annotations are provided, so the description carries a heavier burden. It does disclose the core behavioral effect (restoring deletions and dropping insertions), but it omits important details like whether the change is permanent, how formatting changes are handled, and that the file is modified in place.

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 that gets straight to the point, front-loading the action and providing useful detail without any 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 fully documented schema, the description provides sufficient context to understand the tool's purpose and main effect. It lacks caveats like irreversibility or handling of non-text changes, but is still reasonably complete.

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 already provides 100% coverage for the single parameter 'file_path' with a clear description. The tool description adds no extra parameter semantics beyond referring to the Word document, so the baseline score of 3 is appropriate.

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 ('Reject'), identifies the target resource ('tracked changes in a Word document'), and clarifies the effect ('restoring deletions and dropping insertions'), which distinguishes it from sibling tools like word_accept_all_changes.

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 makes the usage context clear: it is for rejecting all tracked changes in a Word document. However, it does not explicitly mention alternatives or exclusion cases, such as when to use word_accept_all_changes instead.

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