HWP MCP Server

Overview Schema Source Related Servers Discussions Admin

set_page_style

Set page orientation and margins for an open HWP document, specifying portrait or landscape and top, bottom, left, right margins in points.

Instructions

Set page style for the document.

Args: doc_id: Document ID from open_document orientation: "portrait" or "landscape" margin_top: Top margin in pt margin_bottom: Bottom margin in pt margin_left: Left margin in pt margin_right: Right margin in pt

Returns: Style confirmation

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": {
      "doc_id": "<doc_id>"
    },
    "name": "set_page_style"
  }
}

Input Schema

Name	Required	Description	Default
`doc_id`	Yes
`margin_top`	No
`margin_left`	No
`orientation`	No
`margin_right`	No
`margin_bottom`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 31, 2026

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 disclose behavioral implications on its own. It states the operation is a 'set' (mutating) and lists what values can be changed, but it does not explain whether unspecified fields are preserved or reset, whether the change is reversible, or what happens on invalid input.

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 compact and well-organized with a clear Args list and a Returns line. Each parameter earns its place, and the format is easy to parse, although 'Style confirmation' is vague.

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

Completeness3/5

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

The description provides enough to make a basic call: doc_id, orientation, and margins are all explained. However, it omits behavioral details like default handling of omitted margin values, whether orientation and margins can be set independently, and what 'Style confirmation' precisely contains, leaving some uncertainty for an agent.

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?

Schema description coverage is 0%, so the description carries the burden of explaining parameters. It does this well by describing doc_id provenance, orientation's allowed values, and specifying margins in points. It adds meaning beyond the raw schema, though it could note that all parameters except doc_id are optional.

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 operation: setting the page style of a document, with a specific verb and resource. The enumerated arguments (orientation, margins) make the scope concrete, but it does not explicitly distinguish itself from related siblings like set_page_border, set_columns, or set_section_definition.

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?

The only usage guidance is the prerequisite that doc_id comes from open_document. There is no indication of when this tool should be preferred over similar page-layout tools, nor any mention of conditions or exclusions.

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

Deploy Server