Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update print page

update_page

Rename or move a print page within an Ohmstead project, including automatic pages and subsystem drill-down views.

Instructions

Rename or move a print page. page: id or name of a placed page, or an automatic page "auto:0", "auto:1"… (with subsystem for a drill-down view; automatic pages can only be renamed, and an empty name gives back the automatic one).

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>",
      "page": "<page>"
    },
    "name": "update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNo
pageYes
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

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety bar is lower. The description adds genuinely useful behavioral constraints beyond that — auto pages are rename-only and an empty name resets the automatic label. It still omits whether partial updates are allowed (e.g., supplying only x), whether move requires both coordinates, and 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?

Front-loaded with the action, then a single compact parenthetical that carries the parameter rules. No filler sentences and no repetition of schema or annotation content.

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 6-parameter mutation tool with no output schema and thin schema descriptions, the definition covers the core parameter well but leaves coordinate behavior, partial-update semantics, and the response undefined. It is usable but not fully sufficient to call confidently in edge cases.

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 17%, so the description must carry the load. It does explain the trickiest parameter (`page`) in depth, including the "auto:N" form and the subsystem interaction, and hints at name/x/y via "rename or move," but it leaves x, y, name, and project_id without explicit semantics or constraints.

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?

States a specific verb pair and resource: "Rename or move a print page." An agent immediately knows this is the mutation tool for pages versus add_page/remove_page. It does not explicitly name a sibling alternative, but the name-plus-verb pairing is unambiguous.

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 by constraints rather than stated directly: it explains that automatic pages can only be renamed and that an empty name restores the automatic one, which implicitly tells the agent when move is unavailable. There is no explicit when-to-use/when-not guidance or routing to alternatives for page management.

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