Office-MCP-Server

Overview Schema Source Related Servers Discussions Admin

word_set_headings

Set or clear heading levels (1-9) on targeted paragraphs in a .docx file by specifying paragraph IDs and desired levels. Modify multiple paragraphs at once in a single operation.

Instructions

Set or clear a heading style on paragraphs by paraId

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

Input Schema

Name	Required	Description	Default
`edits`	Yes	Heading levels to apply, per paragraph, in one pass
`file_path`	Yes	Absolute path to the .docx file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A3.5/5.0

Behavior2/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 states the action 'set or clear' but doesn't disclose side effects such as modifying the .docx file, potential to overwrite existing heading styles, or any permission requirements. This is a mutation tool with inadequate behavioral disclosure.

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 concise sentence that is front-loaded with the action and object. Every word contributes to meaning, making it highly scannable.

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?

The tool is relatively simple with 2 well-documented parameters and no output schema. However, the lack of usage guidelines and behavioral transparency means the agent might not know when to call this or what happens after execution. It's minimally viable but has clear gaps.

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 description coverage is 100% with both file_path and edits documented, and nested items (para_id, level) also have descriptions. The description adds little beyond the schema, mainly repeating 'by paraId' and mentioning the set/clear behavior which aligns with the level parameter's '0 to clear'.

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 phrase 'Set or clear' and identifies the resource 'heading style on paragraphs' with the key 'paraId'. This clearly distinguishes it from sibling tools like word_set_paragraph_formats which handle broader paragraph formatting.

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 implies usage for heading formatting but provides no explicit guidance on when to use this tool versus alternatives like word_set_paragraph_formats or word_edit_paragraphs. There are no exclusions or alternative recommendations.

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

Deploy Server