inksmcp

Overview Schema Source Related Servers Discussions Admin

page_resize

Resize an SVG document page to specific width and height, keeping drawings centered or top-left and scaling backgrounds. Use for A4 or custom layouts.

Instructions

Set the page size in user units (e.g. 210 x 297 for A4 in a mm document). anchor='center' keeps the drawing centred on the new page; 'top-left'/'none' leave content where it is. Backgrounds are resized.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "page_resize"
  }
}

Input Schema

Name	Required	Default
`width`	Yes
`anchor`	No	top-left
`doc_id`	No
`height`	Yes
`preview`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that anchor='center' keeps the drawing centered, that top-left/none leave content in place, and that backgrounds are resized. But it omits critical mutation details: whether the operation is destructive, what happens to content falling outside the new page, how preview behaves, and any permission requirements.

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 compact and front-loaded: it begins with the core action, then covers anchor behavior and background resizing. Every clause adds useful information, and there is no filler.

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?

For a five-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description covers the core operation and anchor semantics well. It remains incomplete because doc_id and preview are undocumented, and broader side effects or safety behavior are not described.

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 description coverage is 0%, so the description must compensate. It adds meaning for width, height, and anchor, including units and mode semantics, but leaves doc_id and preview unexplained. Partial compensation for three of five parameters justifies a middle 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 states a specific verb and resource: setting the page size in user units. It includes a concrete A4/mm example, making the operation unambiguous. However, it does not explicitly distinguish this from the sibling page_fit tool, so it falls short of a full 5.

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 description explains the anchor options but gives no guidance on when to use this tool versus alternatives such as page_fit or layout. There are no prerequisites, exclusions, or workflow context to help an agent choose correctly.

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