Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove process lines

remove_process_lines
Destructive

Remove P&ID lines using their IDs; list IDs with get_project. Wiring-derived signal lines are not stored here—edit the wiring to change them.

Instructions

Remove lines from the P&ID by id (get_project lists them). Signal lines derived from the wiring aren't stored here; change the wiring to change them.

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>",
      "lines": "<lines>"
    },
    "name": "remove_process_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYesLine ids
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is known. The description adds genuine domain context about derived signal lines not living here, but says nothing about whether removal is reversible, whether dependent connections are cascaded away, or what happens on partial failure.

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 sentences, the action and identifier source front-loaded, followed by the exclusion. Every clause carries information; nothing is restated from the schema or title.

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 removal with no output schema, the description covers the essentials an agent needs: where ids come from and what this tool does not touch. It stops short of describing side effects of deleting a line (e.g., dangling connections), which would fully close the gap for a destructive operation.

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 50%: 'lines' is documented as 'Line ids' while project_id is bare. The description adds meaning by explaining where the ids come from (get_project) and that ids refer to P&ID lines rather than wiring-derived signals, which partially compensates for the undocumented project_id.

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 lines from the P&ID by id') and names get_project as the source of ids. It also carves out a category it does not handle (wiring-derived signal lines), which helps distinguish it from wiring-editing siblings, though it does not explicitly contrast with the other remove_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use path ('by id (get_project lists them)') and an explicit when-not clause: wiring-derived signal lines are not stored here and must be changed via the wiring instead. No exclusions relative to remove_connections or remove_components are stated, but the core routing guidance is present.

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