Skip to main content
Glama
Sign In
Office Word MCP Server

Office Word MCP Server

by GongRzhe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_page_break

Insert a page break in Microsoft Word documents to separate content sections or start new pages where needed.

Instructions

Add a page break to the document.

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": {
      "filename": "<filename>"
    },
    "name": "add_page_break"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
  2. First observed

TDQS

C2.9/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 'Add a page break' which implies a mutation, but doesn't disclose behavioral traits such as whether it modifies the document in-place, requires specific permissions, or has side effects like affecting pagination. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose without any waste. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the complexity of a mutation tool with no annotations, 1 parameter at 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameters, behavioral context, and expected outcomes, making it inadequate for safe and effective use by an AI agent.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It doesn't mention the 'filename' parameter at all, failing to add meaning beyond the schema. However, with only one parameter, the baseline is higher, but the description doesn't explain what 'filename' refers to (e.g., document name or path), resulting in a minimal viable score.

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 clearly states the action ('Add') and resource ('page break to the document'), making the purpose evident. However, it doesn't differentiate from siblings like 'add_paragraph' or 'insert_line_or_paragraph_near_text', which could also affect document structure, so it's not fully specific to sibling context.

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. With siblings like 'add_paragraph' or 'insert_line_or_paragraph_near_text' that might serve similar formatting purposes, the description lacks context on appropriate scenarios or exclusions, offering minimal usage direction.

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