Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove P&ID items

remove_pid_items
Destructive

Deletes items from a P&ID along with every line touching them, while linked wiring components remain in the schematic.

Instructions

Remove items from the P&ID, and every line touching them. Linked wiring components stay in the schematic.

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>",
      "items": "<items>"
    },
    "name": "remove_pid_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesItem tags or ids
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, but the description adds context the annotations cannot: this is a cascading delete that also removes every line touching the items, with the explicit carve-out that linked wiring components remain in the schematic. That is exactly the kind of side-effect detail an agent needs before a destructive call; only the irreversibility/confirmation posture is left unstated.

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, zero filler, with the destructive cascade front-loaded before the exception. Every sentence carries information the agent needs.

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 two-parameter destructive tool with no output schema, the definition covers the essential risk: what is deleted and what is preserved. It is only slightly thin on what qualifies as an 'item' and what the caller gets back after a successful removal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% — 'items' is documented as 'Item tags or ids' while project_id has no description — and the description itself says nothing about either parameter. It does not clarify whether items may be sheets, symbols, or process lines, nor how project_id scopes the operation, so it fails to compensate for the coverage gap.

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?

"Remove items from the P&ID" gives a specific verb and resource, and the second clause scopes the cascade. It does not explicitly distinguish itself from similar siblings such as remove_process_lines or remove_pid_sheet, so an agent must infer the boundary, but the core purpose 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: the tool obviously applies when items must be deleted from the P&ID. There is no statement of when to prefer it over remove_process_lines, remove_components, or remove_pid_sheet, and no prerequisites are mentioned, leaving the agent to infer selection from the names.

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