Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove wires

remove_connections
Destructive

Remove specified wires (grid rows) from a project by project ID and connection IDs. Edits the project's wiring data only; never deletes projects or Codex parts.

Instructions

Remove wires (grid rows) from a project by id. This edits the project; it never deletes projects or Codex parts.

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>",
      "connection_ids": "<connection_ids>"
    },
    "name": "remove_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
connection_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known; the description usefully adds that the blast radius is limited to wires and never deletes projects or Codex parts. It does not say whether removal is reversible, what happens to geometry or dependent objects attached to those rows, or whether the call can partially fail. With annotations carrying the safety flag, this is adequate but not rich.

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 scope, with no filler. The only mild redundancy is restating the name/title ('Remove wires') as the opening phrase rather than adding new information there.

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 simple two-parameter mutation with no output schema, the description covers intent and blast radius, which is most of what matters. It leaves out return/result behavior, id sourcing, and failure semantics for invalid or stale connection ids, so it is serviceable rather than complete.

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 0%, so the description must carry parameter meaning and largely does not. "By id" hints at project_id, but connection_ids is never mentioned: no format, no provenance (where to obtain wire ids), and no note that at least one id is required. An agent must inspect the raw schema and guess at id semantics.

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 wires (grid rows) from a project by id" gives a specific verb, resource, and scoping mechanism, and the clarifying parenthetical maps 'wires' to grid rows. The second sentence bounds what is NOT touched (projects, Codex parts), which helps separate it from remove_components/remove_page. It stops short of naming the natural inverse (add_connections) or a directly competing sibling.

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: you remove wires from a project when you have a project id and wire ids. The negative scope sentence gives a soft signal that this is safe for wire-only edits, but there is no explicit when-to-use vs. alternatives (e.g., remove_cable for cables) and no prerequisites or ordering advice.

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