Skip to main content
Glama

Route the board

route_board

Route under the project's rules and net classes. By default (no nets, no router, none of the single-route options below) it runs the full route pipeline Koppar benchmarks: the learned router on the whole board racing the negotiated router on a copy (the board with fewer open items, then fewer DRC errors, goes on), repair rounds on what stays open, the local finish, copper finishing (0/45/90 runs) and one repair round after it, inside one wall-clock cap: time_budget_s is that cap (default 1200, up to 1500), so the job runs up to about 20 minutes: follow it with get_board_job. The result gives the final unconnected items and DRC errors and a pipeline summary: the counts after the route and after each finish, which arm won, whether the copper finishing was kept. preserve_existing unset keeps the copper of a board that has tracks or vias (the negotiated arm then does not run: it routes from scratch) and routes a board without any from scratch; false routes every net again. nets, router, or any single-route option (pours, rule overrides, via_cost, grid_mm, negotiation_rounds, ml_options, seed_existing, fewest_vias, pairs_first, class_vias) runs ONE route with that router instead, for expert control: nets limits it to those nets; preserve_existing (default true) keeps every track and via already on the board and routes only what is still open. pours: "keep" (the default when the board has zones) keeps the board's zones and routes every net as tracks; "engine" plans a GND pour and fans GND to it by via. Rule overrides apply to this run only. via_cost raises the price of a via in the local router (its default is 2), for fewer vias at some completion cost; the learned router takes its via discipline in ml_options. A single route takes time_budget_s (default 120, up to 900).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netsNoNet names; * and ? wildcards, e.g. ["USB_D*", "+3V3"].
poursNo
routerNoUnset: the full pipeline (above) on the whole board, "ml" for nets. "ml": the learned router service alone, 1 to 8 layers; the time budget is its deadline. Nets outside the nets scope, and with preserve_existing the nets their copper already connects, keep that copper and everything else is routed around it (partial copper of a routed net is replaced). "ts": the local router, also the fallback when the service fails; pours/via_cost/grid_mm/negotiation_rounds apply to it only. "negotiated": PathFinder over every net at once, gridless on a coarse routing graph, the fine grid for the last open nets (the whole board from scratch, nets must be unset; GND routed as a net under its pour, then pruned). Minutes (its budget is 1800 s unless time_budget_s is given) but it closes dense boards the service leaves open. Follow with tidy_copper.
wait_sNoSeconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budget_s, rounds), and survives a server restart (the op starts over from its snapshot).
grid_mmNo
via_costNo
design_idYesThe design id returned by import_kicad_project or list_designs.
class_viasNoRoute with the Default class's via. Without it (and without via_diameter_mm) a route uses the board's smallest legal via where the class's is larger.
ml_optionsNoFields passed to the learned router service as they are (router "ml"): via_cost and via_cost_hi (prices in lattice cells; a move costs 1 and the served default via is 8, 12 while a net is on the quality ladder), ql_release (rejected rip trades before a net drops to via_cost, 0 never), endgame_release (false keeps failing nets at via_cost_hi), economy_via_mm (a via counts as this many mm in the economy pass, default 2), guide_via_w (per-cell via price from the model's via channel), plane_cost (signal copper on a poured layer, per cell), pair_w, guide_w, ripup, seed_offset, via_economy_victims (default 4; 8 trades harder), first_nets (globs routed before everything else: buses that span several connectors), draws (client-side: route this many seeded draws and keep the one that connects most then uses fewest vias; the tie-breaks alone move a 500-via board by about 8 vias), stitch_poured (false: no stitch via for a pad already on a layer poured with its net, GND pads on F/B), stitch_cluster_mm (join same-layer pads of a poured net within this reach by short traces and via once per cluster; 4 wins, 8 loses), stitch_cluster_nets (globs: which poured nets cluster), draw_open_penalty (client-side: vias an open net costs when draws are compared, default 0 = the most-connected draw always wins), layer_cost (per-cell price on named layers, {"F.Cu": 2}: the pour polish prices every layer but the plane's).
fewest_viasNoRouter "negotiated": the fine-grid router alone with its via phase (every net rerouted at 3x the via price and settled again): fewer vias, 2-3x the time.
pairs_firstNoRoute the differential pairs (USB D+/D-, CAN H/L, X_P/X_N) alone first, then everything else around them: a port pad row only lets a pair out before the neighbours take its lane.
clearance_mmNo
via_drill_mmNo
vias_in_padsNo'forbid' (default): no via inside an SMD pad under 2 mm. 'allow': vias may sit in pin pads, for a board ordered with filled and capped vias (JLCPCB POFV); dense connector rows close that otherwise stay open.
seed_existingNoML router: the connected nets in scope are sent as their own routes (seed_copper) and the service reworks the finished board with its rip-up and via-economy passes; kept only when KiCad counts fewer vias. Scope nets to the routed signal nets (pour nets stay).
time_budget_sNoThe full pipeline's wall-clock cap (default 1200), or a single route's budget (default 120, up to 900).
track_width_mmNo
via_diameter_mmNo
edge_clearance_mmNo
preserve_existingNo
negotiation_roundsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wait_s / description
      Previous value: -"Seconds to wait for the job (default 55). A job still running comes back with status \"running\": follow it with get_board_job."New value: +"Seconds to wait for the job (default 55). A job still running comes back with status \"running\": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budget_s, rounds), and survives a server restart (the op starts over from its snapshot)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / router / description
      Previous value: -"\"ml\" (default): the learned router service, 1 to 8 layers; the time budget is its deadline. Nets outside the nets scope, and with preserve_existing the nets their copper already connects, keep that copper and everything else is routed around it (partial copper of a routed net is replaced). \"ts\": the local router, also the fallback when the service fails; pours/via_cost/grid_mm/negotiation_rounds apply to it only. \"negotiated\": PathFinder over every net at once, gridless on a coarse routing graph, the fine grid for the last open nets (the whole board from scratch, nets must be unset; GND routed as a net under its pour, then pruned). Minutes (its budget is 1800 s unless time_budget_s is given) but it closes dense boards the service leaves open. Follow with tidy_copper."New value: +"Unset: the full pipeline (above) on the whole board, \"ml\" for nets. \"ml\": the learned router service alone, 1 to 8 layers; the time budget is its deadline. Nets outside the nets scope, and with preserve_existing the nets their copper already connects, keep that copper and everything else is routed around it (partial copper of a routed net is replaced). \"ts\": the local router, also the fallback when the service fails; pours/via_cost/grid_mm/negotiation_rounds apply to it only. \"negotiated\": PathFinder over every net at once, gridless on a coarse routing graph, the fine grid for the last open nets (the whole board from scratch, nets must be unset; GND routed as a net under its pour, then pruned). Minutes (its budget is 1800 s unless time_budget_s is given) but it closes dense boards the service leaves open. Follow with tidy_copper."
    • addedInput schema / properties / time_budget_s / description
      Added value: +"The full pipeline's wall-clock cap (default 1200), or a single route's budget (default 120, up to 900)."
    • changedInput schema / properties / time_budget_s / maximum
      Previous value: -900New value: +1500
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

With annotations only giving readOnlyHint=false/openWorldHint=false/destructiveHint=false, the description carries the real behavioral load: wall-clock cap semantics (time_budget_s default 1200, up to 1500), that the job runs ~20 minutes and survives a server restart from its snapshot, what the result contains (open items, DRC errors, per-stage counts, which arm won), preserve_existing's effect on copper and the negotiated arm, and per-arm tradeoffs. This is unusually rich disclosure beyond the structured fields.

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

Conciseness2/5

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

The description is a dense run-on cascade of clauses with minimal paragraphing or bullet structure, making it hard to parse even though most content is substantive. The first sentence is well front-loaded, but the remainder reads as an undifferentiated stream rather than an organized parameter/behavior guide.

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 21-parameter, nested-schema, no-output-schema tool, it covers the main modes, follow-up workflow, time-budget behavior, and even summarizes what the result reports. Gaps remain for the geometry/rule parameters and no explicit statement of failure handling, so it is strong but not exhaustive.

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?

At 52% schema coverage the description must compensate, and it does for many parameters: preserve_existing, pours keep/engine, via_cost pricing, nets scoping, time_budget_s defaults, seed_existing, fewest_vias, pairs_first, and the entire ml_options field set. However, several parameters (clearance_mm, track_width_mm, via_drill_mm, edge_clearance_mm, class_vias, via_diameter_mm, vias_in_pads, wait_s) get little or no added meaning, leaving real gaps.

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 opening sentence states a specific verb and resource (route the board under the project's rules and net classes) and immediately distinguishes two operating modes: the default full pipeline versus a single route selected by nets/router/single-route options. It also names follow-up siblings (get_board_job, tidy_copper), though it never explicitly contrasts itself with other routing siblings like repair_board, ripup_routing, or tidy_copper. Purpose is clear but the density of detail partly buries it.

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 concrete when-to-use guidance: default = full pipeline; setting nets/router or any single-route option triggers one expert-controlled route; 'negotiated' is recommended for dense boards the service leaves open; the default flow should be followed with get_board_job. It does not state clear when-NOT-to-use conditions or compare against sibling routing/repair tools, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources