docx-mcp-server

Overview Schema Source Related Servers Discussions Admin

apply_document_preset

Apply a named document style preset in one pass to set a document-wide baseline, replacing repeated paragraph-level formatting.

Instructions

Apply a named document style preset in one pass by updating styles.xml. Use this instead of repeated paragraph-level formatting when you want a document-wide baseline.

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

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Absolute path to the .docx file
`preset`	Yes	Preset name. 'ja-business' applies Yu Gothic body defaults plus roomier paragraph and heading spacing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0May 29, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states 'in one pass by updating styles.xml', implying modification of document styles but doesn't disclose side effects like overwriting existing styles or irreversibility.

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?

Two sentences, no wasted words. Front-loaded with action and purpose, efficient structure.

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

Completeness5/5

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

For a simple tool with 2 parameters and no output schema, the description covers purpose, usage, and preset details adequately. No gaps given the low complexity.

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

Parameters4/5

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

Schema coverage is 100%, and description adds value by explaining the 'preset' parameter with specific details (e.g., 'ja-business' applies Yu Gothic body defaults plus spacing) beyond the enum.

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 'Apply a named document style preset' and explicitly distinguishes from siblings like set_paragraph_formats by recommending it 'instead of repeated paragraph-level formatting' for 'document-wide baseline'.

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?

Explicit guidance to use instead of repeated paragraph-level formatting for document-wide baseline. Could be improved by noting when not to use (e.g., selective formatting), but provides clear context.

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