Skip to main content
Glama

pcb_route_push_chain

Destructive

Plan or apply bounded movement of up to eight allowed isolated pad-to-pad traces on TOP/BOT; preserve anchors and other copper, and require exact replacement plus fresh DRC for apply.

Instructions

Plan/apply bounded multi-trace chain displacement on TOP/BOT. Up to eight explicitly allowed, current MCP-created isolated pad-to-pad traces may move internal orthogonal segments; fixed anchors and all other copper/vias are preserved. mode=plan is read-only, apply requires exact replacement and fresh native DRC. Not the vendor interactive engine; branch/via push and arbitrary locked traces remain unsupported. NOT atomic. 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_chain"
  }
}

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.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=false, destructiveHint=true; the description adds material context the agent cannot infer: the operation is NOT atomic, disk state requires save/reopen verification, and preserved anchors/copper are guaranteed in-contract. It also reconciles the destructive hint with the read-only plan mode, which is exactly the nuance an agent needs before invoking.

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 purpose, then constraints, then caveats, with no filler sentences. The telegraphic style ('NOT atomic. Save/reopen for disk verification.') is information-dense but borders on clipping, which slightly hurts readability.

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?

For a 13-parameter, mutating geometry tool with no output schema, the description covers the workflow contract well (plan vs apply, DRC, non-atomicity) but leaves the return shape, token semantics, and units/meaning of the numeric geometry parameters unaddressed. Adequate for a careful caller, incomplete for one that must construct a valid first call.

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 0%, so the description must carry parameter meaning, and it only partially does: it explains mode semantics, constrains movable_wire_ids to at most eight MCP-created isolated pad-to-pad traces, and clarifies that points_nm denote internal orthogonal segments. It says nothing about expected_token (a required optimistic-concurrency field), session, grid_nm, width_nm, clearance_nm, or max_displacement_nm, leaving several required and safety-relevant parameters opaque.

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 and resource: plan/apply of bounded multi-trace chain displacement on TOP/BOT. It also narrows scope sharply (only MCP-created isolated pad-to-pad traces, max eight), which lets an agent rule it out quickly. It does not explicitly contrast against the closest sibling pcb_route_push, so it stops short of full sibling differentiation.

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?

Gives clear operating conditions: mode=plan is read-only, apply requires an exact replacement plus a fresh native DRC, and usage is bounded to eight explicitly allowed movable wires. It also states exclusions ('branch/via push and arbitrary locked traces remain unsupported'), which is strong negative guidance. It never names an alternative tool to use when those exclusions apply, so it is not a full when/when-not/alternative pairing.

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