Skip to main content
Glama

autoroute

Routes unrouted PCB connections as one change—whole board, selected nets, parts, or one instance—then names failures and reasons so you can fix and retry.

Instructions

Route the unrouted connections as ONE change: the whole board, or only some nets, parts or one instance (one of these). Run it after placing; parts with no position get no copper; existing copper is kept. It names each connection it could not route, with the reason: route those with route_track, or move parts and run it again.

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": "autoroute"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
netsNoe.g. ["VBUS"]
partsNoe.g. ["U1"]
instanceNoe.g. "PS1"; copied to its sheet's other instances placed alike
budgetSecondsNoDefault 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses atomicity ("as ONE change"), non-destructiveness ("existing copper is kept"), a silent-skip case (parts with no position get no copper), and the failure channel (it names each unrouted connection with a reason). That covers side effects, safety, and outcome reporting that the schema cannot express.

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?

Three dense sentences, front-loaded with the core action and scope, then prerequisites, then failure handling — no filler. The compression is occasionally terse ("parts with no position get no copper"), trading a little readability for brevity.

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 5-parameter mutation tool with no output schema, the description covers scope, prerequisites, side effects, and return content well. The one gap is budgetSeconds behavior — the schema states a default of 20 and a 300 cap, but nothing says what happens to a run that exceeds the budget.

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% with per-parameter examples and a documented default, so the schema already does most of the work. The description still adds genuine semantics the schema lacks — that the nets/parts/instance selectors are mutually exclusive ("one of these") rather than combinable filters.

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?

"Route the unrouted connections" gives a specific verb and resource, and the description immediately bounds the scope (whole board, or a subset of nets/parts/instance). It is clearly distinguishable from route_track, which it names as the tool for connections this one could not handle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the prerequisite ("run it after placing"), the exclusivity of the scope selectors ("one of these"), and the recovery paths — use route_track on failed connections, or move parts and re-run. When-to-use and what-to-do-on-failure are both explicit.

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