Skip to main content
Glama

unroute

Destructive

Removes routed copper for selected nets or all nets in one change while preserving hand-drawn and locked copper.

Instructions

Remove the router's copper, for some nets or all, as ONE change. Hand-drawn and locked copper stay.

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

Input Schema

NameRequiredDescriptionDefault
allNo
fileYesCircuit file
netsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 valuable specifics beyond that: the operation is atomic ("as ONE change") and hand-drawn and locked copper is preserved. It does not state whether the removal is reversible or what the response contains.

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, with the preservation caveat second. No wasted wording; slightly terse to the point of leaving edge cases implicit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 3-parameter tool with only 33% schema coverage and no output schema, the description leaves key questions open: precedence between nets and all, error behavior if nets don't exist, and whether the removal is undoable. It is directionally helpful but incomplete for a mutation tool.

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 only 33% (only file is described as "Circuit file"). The description clarifies the semantic relationship between all and nets (some nets vs all), which helps, but does not explain the boolean all flag explicitly or whether nets is mutually exclusive with all.

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+resource: remove the router's copper from nets or all nets, in one change. It distinguishes itself from removal of hand-drawn/locked copper, though it doesn't name a sibling tool to contrast with.

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?

Implies usage via the all/nets distinction (remove from some nets or all), but gives no explicit when-to-use or when-not-to-use guidance relative to siblings like autoroute or edit_circuit.

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