Skip to main content
Glama

remove_copper

Destructive

Remove tracks and vias by ID from copper_summary or check_circuit in a single change; locked copper is refused.

Instructions

Remove tracks and vias by id (from copper_summary or check_circuit) as ONE change; { id, segment } removes one segment. Locked copper is refused.

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": {
      "file": "<file>",
      "ids": "<ids>"
    },
    "name": "remove_copper"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIds, or { id, segment }
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true; the description adds real behavioral detail beyond that by stating the operation is a single atomic change and that locked copper is refused, which tells the agent to expect partial-failure semantics. It does not describe what the response looks like or whether changes are undoable.

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 dense sentences with no filler: the verb and resource come first, followed by the id source and the object-form special case. Every clause 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 full schema coverage and no output schema, the description covers source of ids, atomicity, and the locked-copper failure case. Return value and post-removal state are not addressed, but that is a minor gap given the tool's simplicity.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by explaining that the object form { id, segment } targets exactly one segment of an item, complementing the schema's note that segment 0 is the first point to the second. It also clarifies that ids originate from copper_summary or check_circuit.

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 tracks and vias by id') and notes the atomic scope ('as ONE change'), which distinguishes it from piecemeal removal. It does not explicitly contrast with sibling tools like remove_trace or remove_pour, leaving some ambiguity about which remover to pick.

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 clear operational context: ids must come from copper_summary or check_circuit, and the call is treated as one atomic change. It stops short of stating when to prefer this over remove_trace for a single track, so exclusions are absent.

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