Skip to main content
Glama
Sign In
Office-MCP-Server

Office-MCP-Server

by stoyantsiparov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_get_page_layout

Retrieve page size, orientation, and margins from a Word document to review or verify its layout settings.

Instructions

Read page size, orientation, and margins for a Word 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": {
      "file_path": "<file_path>"
    },
    "name": "word_get_page_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the .docx file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. The verb 'Read' implies a non-destructive operation, but the description does not disclose potential errors, file handling behavior, or side effects. It conveys safety but lacks rich behavioral context.

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, focused sentence that directly states the tool's function. No filler or redundancy; it earns its place.

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?

Given the tool's simplicity (one parameter, no output schema), the description sufficiently communicates what the tool reads: page size, orientation, and margins. However, it does not specify the return format or structure, but this is not strictly necessary for such a simple getter. The presence of sibling tools like word_set_page_layout provides helpful contrast.

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 100%: the single parameter file_path is described as 'Absolute path to the .docx file'. The description adds no additional meaning beyond this, so the baseline of 3 applies.

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 uses a specific verb 'Read' and clearly identifies the resource: 'page size, orientation, and margins for a Word document'. This distinguishes it from sibling tools like word_set_page_layout (which writes) and word_get_document_info (which covers broader document info).

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

Usage Guidelines3/5

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

The description implies usage context (when you need page layout details), but it does not explicitly state when to use this tool over alternatives or mention any exclusions. For a simple read operation, the implied usage is clear, but no direct comparison to siblings like word_set_page_layout is provided.

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