Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove components

remove_components
Destructive

Delete devices or terminal strips by tag along with all their wires and cables. Removes rack modules of a deleted PLC and unlinks P&ID items; nothing is deleted if any tag is unknown.

Instructions

Delete components (devices or terminal strips) by tag, with every wire and cable on them. Modules in a removed PLC's rack come out of it; linked P&ID items stay and are unlinked. Nothing is deleted if any tag is unknown.

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>",
      "tags": "<tags>"
    },
    "name": "remove_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true, and the description goes well beyond them: it discloses the cascade scope (wires and cables), the rack consequence (modules of a removed PLC come out), the treatment of external references (linked P&ID items survive but are unlinked), and an all-or-nothing rule ('Nothing is deleted if any tag is unknown'). That last detail is exactly the kind of precedent an agent needs before a destructive bulk call.

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?

Three short sentences, front-loaded with the action and its cascade, followed by the two edge cases that matter most. No filler or restatement of the tool name.

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 destructive, two-parameter bulk operation with no output schema, the description covers scope, side effects, and failure semantics well. It stops short of saying what a successful call returns (e.g., counts or the removed tags), which would help an agent confirm the outcome, but nothing critical to invoking it correctly is missing.

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 description coverage is 0%, so the description must carry the meaning. It clarifies that `tags` are component tags and that the operation is batch-oriented with atomic failure across the whole set, but `project_id` is never mentioned and no tag format or case-sensitivity hints are given. Partial compensation, not full.

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?

The description gives a specific verb (Delete), a concrete resource set (components = devices or terminal strips), and the lookup key (by tag). It also draws the boundary against nearby deletion siblings by stating that all wires and cables on the component go with it, so an agent can distinguish it from `remove_cable` or `remove_connections` without opening a schema.

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: the phrase 'by tag' and the bulk cascade signal that this is the right tool when a whole tagged component should disappear. There is no explicit when-to-use vs when-to-prefer-`remove_cable`/`remove_connections` guidance and no mention of prerequisites or required permissions.

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