Skip to main content
Glama

analyze_pcb_nets

Inspect PCB routing to summarize track widths, via drills and spans, net lengths by layer, and compare them against board design rules.

Instructions

Give the routing of a board: track widths, vias, net lengths and layers.

The tool gives the distribution of the track widths and of the via drills, the layer spans of the vias, the tracks of each layer, the nets by the length of their tracks, and a comparison with the design rules of the board.

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_path": "<file_path>"
    },
    "name": "analyze_pcb_nets"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesThe .kicad_pcb file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It discloses in detail what gets computed and compared against the board's design rules, which is genuine behavioral context, but it never states that the file is only read and not modified, whether any preconditions exist (e.g., board must contain routed tracks), or how missing design rules are handled.

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 first sentence is a good front-loaded summary, but the second is a single long run-on that repeats categories already named (track widths, vias) while piling on subordinate clauses. It is parseable but could be a compact list without the repetitive "the ... and of the ..." construction.

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 one-parameter read-only analysis tool with an output schema present, the description is close to complete: it tells the agent what report categories come back and that design rules are part of the comparison. Only preconditions and units/format of the length figures are left unmentioned, which the output schema likely covers.

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?

There is a single parameter (file_path) with 100% schema description coverage, so the schema already explains it as "The .kicad_pcb file." The description adds nothing about the path's expected form, relative vs absolute resolution, or file-read failure behavior; per the high-coverage baseline this stays at 3.

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 opens with a concrete verb+resource: "Give the routing of a board," then enumerates the concrete artifacts produced (track width distribution, via drill distribution, via layer spans, per-layer tracks, nets by track length, design-rule comparison). This clearly separates it from signal-integrity, power-integrity, or generic statistics siblings by content, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no exclusion, and no pointer to competing analysis tools such as analyze_pcb_signal_integrity. An agent must infer from the output list that this is the routing-geometry report, which is possible but not guided.

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