Skip to main content
Glama
Sign In
grp-docx-mcp

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_document_outline

Extract a document's heading structure as a flat list of headings. Specify the maximum heading level to include, and receive each heading's level, text, and paragraph ID.

Instructions

Return a flat list of headings as a document outline.

Walks the document body and returns every heading paragraph up to the specified level.

Args: max_level: Maximum heading level to include (1–6, default 6).

Returns: JSON list of dicts with keys: level (int), text (str), para_id (str).

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": "get_document_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_levelNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic operation (walking document body, returning headings) without mentioning side effects, performance, limits, or error handling. The description is minimal and does not add depth beyond the core function.

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?

The description is moderately concise but includes an Args and Returns section that partially duplicates the schema and output description. It could be streamlined while retaining the essential information.

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 tool with one optional parameter and an output schema, the description covers the return structure (list of dicts with keys). However, it lacks details on edge cases (e.g., no headings, invalid max_level) which would be helpful for completeness.

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 'max_level' parameter is explained with a range (1–6) and default value (6), which adds meaning beyond the input schema's title and default. Schema coverage is 0%, so the description compensates well by clarifying the parameter's purpose and constraints.

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 the verb 'Return' and the resource 'headings as a document outline'. It specifies that it returns a flat list, walks the document body, and includes headings up to a specified level, making it distinct from siblings like 'get_headings' which likely returns headings in a different format.

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 to use this tool versus alternatives like 'get_headings' or 'get_all_paragraphs'. It does not mention when not to use it or any prerequisites.

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