Skip to main content
Glama

pcb_route_push

Destructive

Locally push one isolated MCP-created trace to clear a new pad-to-pad path. Plan previews changes without copper edits; apply displaces a bounded orthogonal segment and requires a clean DRC.

Instructions

Bounded local push of ONE isolated MCP-created trace on TOP/BOT to clear an explicit new pad-to-pad path. mode=plan (default) does NOT change copper; mode=apply displaces an internal orthogonal segment, fixes both old pad endpoints, imports exact replacements and requires a fresh clean native clearance DRC. Supply current pcb_read token and explicit movable wire_ids from wire_inventory. No branches, via moves, cascades, arbitrary native/protected traces, native lock certification, or vendor interactive push engine. Non-atomic; an unconfirmed apply may have changed the board. Save/reopen for disk verification.

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>",
      "points_nm": "<points_nm>",
      "movable_wire_ids": "<movable_wire_ids>"
    },
    "name": "pcb_route_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
netYes
modeNo
layerYes
to_padYes
grid_nmNo
sessionYes
from_padYes
width_nmNo
points_nmYes
clearance_nmNo
expected_tokenYes
movable_wire_idsYes
max_displacement_nmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive=true, but the description adds substantive detail beyond them: apply displaces an internal orthogonal segment, fixes both old pad endpoints, imports exact replacements, and requires a fresh clean native clearance DRC. It also discloses non-atomicity ('an unconfirmed apply may have changed the board') and the save/reopen verification step — exactly the risk context a mutation tool needs.

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?

Front-loaded with the core operation and tightly written with no filler. However, the second sentence is a dense run-on packing mode semantics, mutation behavior, and DRC requirements, which costs some readability for an agent parsing quickly.

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 destructive, non-atomic 13-parameter mutation tool with no output schema, the description covers the safety model, mode split, preconditions, and verification workflow well. The remaining gap is parameter-level meaning for the geometry/limit fields, which no other structured field supplies.

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 0% across 13 parameters, so the description must carry the burden. It clarifies mode, expected_token (pcb_read token), movable_wire_ids (from wire_inventory), and layer TOP/BOT, but says nothing about points_nm, grid_nm, width_nm, clearance_nm, max_displacement_nm, net, or session — half the geometry parameters remain opaque.

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?

States a precise verb+resource+scope: 'Bounded local push of ONE isolated MCP-created trace on TOP/BOT to clear an explicit new pad-to-pad path.' The word 'ONE' and 'bounded local' immediately separate it from pcb_route_push_chain, and the explicit exclusion of 'branches, via moves, cascades' reinforces the boundary.

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?

Gives explicit mode semantics (plan default does not change copper; apply mutates), prerequisites ('Supply current pcb_read token and explicit movable wire_ids from wire_inventory'), and a clear when-not list (no branches, via moves, cascades, arbitrary native/protected traces). An agent can decide plan vs apply vs a sibling tool from the description alone.

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