Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove P&ID sheet

remove_pid_sheet

Remove a placed P&ID sheet by ID or name while its items stay on the drawing and move to automatic sheets.

Instructions

Remove a placed P&ID sheet by id or name. Its items stay on the drawing and move to the automatic sheets.

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>",
      "sheet": "<sheet>"
    },
    "name": "remove_pid_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: items are not deleted but stay on the drawing and migrate to automatic sheets, which explains why destructiveHint=false despite a "remove" verb. It does not state reversibility or whether the sheet id/name must be unique.

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?

Two short sentences, front-loaded with the action and immediately followed by the non-obvious side effect. No wasted wording.

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 simple two-parameter mutation with annotations and no output schema, the description covers the essential behavior and the surprising side effect. The only gap is the unexplained project_id parameter.

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 0%, so the description must compensate; it clarifies that the sheet parameter accepts either an id or a name, which is useful. However, project_id is never mentioned, leaving one of two required parameters undocumented.

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?

States a specific verb and resource ("Remove a placed P&ID sheet") and adds the key scope detail that items are preserved rather than deleted, which distinguishes it from remove_pid_items.

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?

Implies usage (removing a placed sheet) and clarifies the consequence, but gives no explicit when-to-use vs. siblings like remove_pid_items or update_pid_sheet, nor any prerequisites.

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