Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add print page

add_page

Place a fixed 1504×800 print page at x, y in a view; blocks centered inside print on it and remaining blocks go to automatic pages in order added.

Instructions

Place a print page: a fixed 1504 × 800 frame in one view with its top-left at x, y (absolute view coordinates, as layout_view's ax, ay and frames). Blocks whose centre is inside print on it; the rest go on automatic pages after the placed ones. Pages print in the order they were added within each view.

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": {
      "project_id": "<project_id>",
      "name": "<name>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "add_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameYes
subsystemNoSubsystem whose drill-down view this is (name or id). Omit for the project view.
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, destructive=false, openWorld=false); the description goes well beyond that by disclosing the fixed frame size, the coordinate space being absolute view coordinates tied to layout_view's ax/ay, the block-assignment rule ('blocks whose centre is inside'), and print ordering within a view.

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?

Three dense sentences, front-loaded with the core action and geometry before the placement and ordering rules. No filler, though the parenthetical coordinate cross-reference is slightly compressed and would read better split out.

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?

For a 5-parameter mutation tool with no output schema, the description covers the geometry, placement algorithm and ordering that an agent needs to call it correctly. Gaps remain around the name parameter and what the call returns (page id? the located page?), but the risky behaviour is fully disclosed.

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 only 20%, so the description carries most of the burden: it defines x and y precisely as absolute view coordinates consistent with layout_view. However, 'name' (required, minLength 1) and 'project_id' get no explanation at all, and the description never says whether names must be unique within a view.

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?

Specific verb plus resource ('Place a print page') and immediately quantifies what a page is: 'a fixed 1504 × 800 frame in one view with its top-left at x, y'. That definitional detail separates it from remove_page/update_page and from the implicit auto-pagination behaviour.

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?

Usage is only implied: the note that unplaced blocks 'go on automatic pages after the placed ones' tells the agent this tool is the manual override, but it never states when to prefer this over automatic paging, nor what happens if the call is made against a view that already has pages. No sibling is named as an alternative.

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