Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove print page

remove_page
Destructive

Delete a placed print page by ID or name while keeping its blocks in place so they print on automatic pages.

Instructions

Remove a placed print page (id or name). Its blocks stay where they are and print on automatic pages.

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": "remove_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the genuinely useful detail that the page's blocks are not destroyed and will print on automatic pages. It does not say whether the removal is reversible or how a missing page is reported.

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?

Two short sentences, front-loaded with the action and its consequence, with no filler. The trailing clause 'print on automatic pages' is slightly cryptic but still earns its place as side-effect information.

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 destructive three-parameter mutation with no output schema, the definition covers the key side effect but omits return behavior, error handling for unknown pages, and the meaning of the subsystem parameter in this removal context. It is adequate but not complete.

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 33%, so the description carries extra burden; it does clarify that 'page' accepts either an id or a name, which the schema leaves blank. However, project_id and subsystem are not discussed, leaving two of three parameters to the schema's minimal text.

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 and resource ('Remove a placed print page') and even clarifies the identifier form ('id or name'). It is distinguishable from add_page and update_page by the verb alone, though it never names those siblings explicitly.

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 implied rather than stated: it is the removal counterpart to placing a page, and the note that blocks remain and print on automatic pages hints at when this is preferable to deleting blocks. There is no explicit when-to-use/when-not framing or named alternative.

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