docx_mcp_server_ts

docx.headers_footers_list

Retrieve a complete list of headers and footers from a DOCX file. Use this to inspect document structure and locate header/footer content for review or further processing.

Instructions

List headers/footers

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docx.headers_footers_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 21, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only repeats the action 'List' and provides no detail about side effects, intermediate state touched, return behavior, or scope of the listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is extremely concise and contains no filler words, but it is under-specified. The sentence is not genuinely informative beyond the tool's name, crossing the line from concise to minimal.

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

Completeness2/5

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

The bare phrase 'List headers/footers' lacks important context such as what the list contains, whether it can for current document state only, and how it relates to headers_footers_get/set. Since there is no output schema, the description should give more indication of the return value or typical use case.

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?

The input schema has zero parameters and 100% coverage, so there is nothing additional the description needed to explain about parameters. The empty schema fully describes the calling signature.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'List' with resource 'headers/footers', making the basic action clear. It broadly distinguishes itself from the get/set sibling tools, though it does not clarify what exactly will be listed or eliminated.

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

Usage Guidelines2/5

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

No guidance is provided on when this tool is appropriate or why it should be selected over headers_footers_get or headers_footers_set. The context signals show no usage direction, so an agent is left to infer the tool's role.

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