Skip to main content
Glama

route_track

Draw a copper track for one net by hand as a single change: set corners on one layer or connect pads, let the router find the path, and list copper violations. Use when autorouting cannot finish a net.

Instructions

Copper track (not a schematic trace): draw one of a net by hand as ONE change: corners on one layer, or from and to pads (via: corners between; none: the router finds the path or says what is in the way). It starts on the net's copper, not a locked part's pad, and touches no other net. The answer lists copper violations. For what autoroute could not route.

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

Input Schema

NameRequiredDescriptionDefault
toNo
netNoNeeded with points
viaNoCorners between from and to; none: the router finds the path
fileYesCircuit file
fromNoe.g. "C3.pin2" or "U2.GND"
layerNoNeeded with points; inner1, inner2 only on 4 layers
widthNomm; default the net class's
pointsNoCorners in mm; the first on the net's copper

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses meaningful behavior: atomicity ('as ONE change'), placement constraints ('starts on the net's copper, not a locked part's pad, and touches no other net'), the return ('lists copper violations'), and the fallback when no vias are given ('the router finds the path or says what is in the way'). It omits permissions or reversibility details, but the safety profile is reasonably conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and there is no filler, but the three-sentence body is packed with nested parentheticals and clipped phrasing ('corners on one layer, or from and to pads (via: corners between; none: ...)'), making it slow to parse.

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 an 8-parameter mutation with no annotations and no output schema, the description covers what is drawn, constraints, failure behavior, and the shape of the answer ('lists copper violations'). That is close to sufficient, though the interaction between points/from/to/via modes could be spelled out more cleanly.

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 description coverage is 88%, so the baseline is 3. The description reinforces a few semantics ('from and to pads', the via/none routing distinction) but mostly echoes what the schema already documents rather than adding new syntax or format guidance.

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 states a specific verb+resource, 'Copper track (not a schematic trace): draw one of a net by hand as ONE change', which distinguishes it from the schematic-oriented add_trace sibling. The overall intent is legible despite dense parentheticals.

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?

The closing line 'For what autoroute could not route' explicitly names the sibling alternative and the condition that selects this tool (manual routing after autoroute failure). There are no broader exclusions, but the primary when-to-use trigger is clear.

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