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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_section_break

Insert a section break at a specific paragraph to control document layout with types like next page, continuous, even or odd page.

Instructions

Add a section break at a paragraph. break_type: nextPage/continuous/evenPage/oddPage.

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": {
      "para_id": "<para_id>"
    },
    "name": "add_section_break"
  }
}

Input Schema

NameRequiredDescriptionDefault
para_idYes
break_typeNonextPage
document_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only lists break types but fails to mention side effects such as impact on headers/footers, page numbering, or document structure. The behavioral impact is not explained.

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

Conciseness4/5

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

The description is a single sentence followed by a succinct list of break type options. It is front-loaded with the main action and avoids unnecessary words, though it could slightly improve readability by separating the list more clearly.

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?

Despite the tool's structural significance, the description does not cover the impact of adding a section break on document sections, headers/footers, or page numbering. It lacks context on when to use different break types or what the output schema returns.

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 coverage is 0%, so the description must add meaning. It explains the 'break_type' parameter by listing its possible values ('nextPage/continuous/evenPage/oddPage'), which clarifies a non-obvious enum. However, 'para_id' and 'document_handle' are not described at all, leaving gaps.

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 'Add' and the resource 'section break', and specifies the location 'at a paragraph'. It distinguishes itself from sibling tools like 'add_page_break' and 'delete_section_break' by focusing on section breaks specifically.

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 'add_page_break' or 'set_section_properties'. The description does not explain the context for selecting different break types 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