Skip to main content
Glama

analyze_pcb_signal_integrity

Analyzes a .kicad_pcb file to find differential pairs, RF tracks, longest signal nets, and via-heavy nets, including differential-pair length mismatch for signal-integrity review.

Instructions

Give the differential pairs, the RF tracks and the longest signal nets of a board (heuristic).

The tool finds a differential pair from the names of two nets (for example USB_P and USB_N, DP and DN) and gives the difference of their lengths. It finds an RF track from the name of its net. It also gives the longest signal nets and the nets with the most vias.

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_signal_integrity"
  }
}

Input Schema

NameRequiredDescriptionDefault
net_nameNoOptional name of one net to analyze in detail.
file_pathYesThe .kicad_pcb file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the important trait that results are heuristic and that pairs/RF tracks are detected from net naming conventions (USB_P/USB_N, DP/DN). It omits cost, parsing scope, and any caveats about false positives from naming heuristics, so the disclosure is partial.

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?

The output summary is front-loaded in the opening sentence and the follow-up sentences explain each detection method. Slight redundancy in the repeated 'It finds / It also gives' phrasing, but no wasteful filler.

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?

An output schema exists, so return values need not be described; the description nevertheless lists the output categories an agent will get. For a two-parameter read-only analysis tool, the main remaining gap is guidance on sibling selection, which is minor given the stated scope.

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 100%, so both parameters are already documented, establishing a baseline of 3. The description adds a little meaning by explaining how net names drive pair/RF detection, but it never clarifies what the optional net_name parameter changes in the output beyond 'analyze in detail'.

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 first sentence names the concrete outputs (differential pairs, RF tracks, longest signal nets) on a board and adds a 'heuristic' qualifier. This distinguishes it reasonably from analyze_pcb_power_integrity and analyze_pcb_nets by naming signal-integrity quantities, though it never explicitly contrasts with those siblings.

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?

Usage is implied rather than stated: an agent can infer 'use this for signal-integrity style net analysis' from the listed outputs. There is no explicit when-not or pointer to alternative tools like analyze_pcb_nets or find_tracks_by_net, so selection between close siblings is left to inference.

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