Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Remove cable

remove_cable
Destructive

Removes a cable and its conductors from a project while leaving connectors on their parts; terminal-end conductors remain as loose wires.

Instructions

Remove a cable and its conductors from a project (the connectors stay on their parts). A terminal-end cable's conductors stay as loose wires. 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>",
      "cable": "<cable>"
    },
    "name": "remove_cable"
  }
}

Input Schema

NameRequiredDescriptionDefault
cableYesCable tag (W1) or id
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, and the description adds genuinely useful detail beyond that: connectors remain attached, terminal-end conductors become loose wires, and projects/parts are never deleted. It stops short of saying whether the removal is reversible or whether connections on the cable are also cleared.

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 consequence on conductors and connectors. No filler or repetition.

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 mutation with annotations and no output schema, the description covers effect scope and non-effects (parts and projects preserved). The remaining gap is that project_id carries no explanation anywhere, and the return value is unstated though no output schema exists.

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 coverage is 50%: the cable parameter is documented as 'Cable tag (W1) or id' while project_id is undocumented. The description adds nothing about either parameter, not even that the cable may be specified by tag or id, 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?

The description gives a specific verb and resource ('Remove a cable and its conductors from a project') and scopes the effect by noting what survives ('the connectors stay on their parts'). It does not name any sibling such as add_cable or remove_connections, so the agent must infer the boundary from the name alone.

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 by the removal verb and the clarifying statement that it edits the project but never deletes projects or Codex parts, which rules out some misuse. There is no explicit when-to-use versus remove_connections or remove_components guidance, nor any prerequisite or confirmation guidance.

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