grp-docx-mcp

Overview Schema Source Related Servers Discussions Admin

set_page_orientation

Change document page orientation to portrait or landscape, automatically adjusting dimensions for selected section or entire document.

Instructions

Set page orientation, swapping width/height dimensions if needed.

Args: orientation: "portrait" or "landscape". para_id: paraId of paragraph with section break. None = body section.

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": {
      "orientation": "<orientation>"
    },
    "name": "set_page_orientation"
  }
}

Input Schema

Name	Required	Description	Default
`para_id`	No
`orientation`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.4Jul 10, 2026

TDQS

A4.6/5.0

Behavior4/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 discloses that width/height dimensions are swapped, which is a key behavioral trait. However, it does not mention potential side effects like impact on margins or reflow, but for a simple mutation this is acceptable.

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 extremely concise: two sentences plus an args block. Every word serves a purpose, and it is well-structured with clear bullet-point-like arguments.

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

Completeness5/5

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

Given the tool's simplicity, the existence of an output schema, and the clear sibling context (many 'set_' tools), the description provides all necessary information. It covers purpose, parameters, and behavioral detail sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, leaving the description responsible for parameter meaning. The args block explicitly defines orientation as 'portrait' or 'landscape' and clarifies para_id as paragraph with section break or body section, adding critical value beyond the schema titles.

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 'Set page orientation, swapping width/height dimensions if needed.' It specifies the verb (set) and the resource (page orientation), and the mention of dimension swapping distinguishes it from similar tools like 'set_page_size'.

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

Usage Guidelines4/5

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

The description explains the orientation parameter values and the optional para_id with its default (None = body section), providing clear context for usage. It does not explicitly list when not to use or alternatives, but the purpose is implicit and adequate for this simple tool.

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

Deploy Server