Skip to main content
Glama

pcb_route

Destructive

Adds verified same-layer copper routing between two native pads on an ARES PCB. Checks pad, via, copper, and edge clearances while preserving existing wires and calibrated vias.

Instructions

Add verified real TOP/BOT same-layer copper in the owned ARES board, preserving old wires and calibrated vias. Token, existing net and two native pad ids required. Explicit points_nm or conservative 8-direction A*. All pad/copper/via/edge clearance checked. Integer nm must be 10 nm aligned. Not full DRC or push/shove. Unknown geometry fails closed; NOT atomic. Save/reopen verifies disk copper.

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": {
      "session": "<session>",
      "expected_token": "<expected_token>",
      "net": "<net>",
      "layer": "<layer>",
      "from_pad": "<from_pad>",
      "to_pad": "<to_pad>"
    },
    "name": "pcb_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
netYes
layerYes
to_padYes
grid_nmNo
sessionYes
from_padYes
width_nmNo
points_nmNo
clearance_nmNo
expected_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already mark it destructive and non-read-only; the description adds concrete behavior: preserves existing wires and calibrated vias, checks clearances, fails closed on unknown geometry, is not atomic, and verifies disk copper after save/reopen. These are exactly the operational risks an agent needs beyond the annotations.

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?

The definition is dense but front-loaded: purpose, prerequisites, routing mode, constraints, and limitations arrive in short sentences with no filler. Every sentence contributes operational information.

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

Completeness3/5

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

It covers behavior and safety well for a complex destructive tool, but with no output schema it never explains the return or verification payload, and several parameters remain undocumented. An agent can grasp the risks but still lacks full call-time completeness.

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?

With 10 parameters and 0% schema description coverage, the description names net, layer, pad ids, token, and points_nm but leaves width_nm, clearance_nm, grid_nm, session, and expected_token semantics largely unexplained. It adds useful unit and alignment context but does not 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?

States a specific verb ('Add') and resource ('TOP/BOT same-layer copper') in the owned ARES board, with clear scope limits. It implicitly distinguishes basic routing from push/shove routing, but does not name a sibling alternative, so it falls short of 5.

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?

Provides required inputs and notes the tool is not full DRC or push/shove, giving some usage boundary. It does not say when to choose this over pcb_route_push, pcb_route_push_chain, or pcb_route_layers, leaving alternative selection to inference.

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