Skip to main content
Glama

analyze_pcb_power_integrity

Extract copper zones and power-net routing from a KiCad PCB file to inspect power and ground distribution. Identifies VCC, VDD, VBUS, and GND nets by name for power integrity review.

Instructions

Give the copper zones of a board and the routing of its power nets (heuristic).

The tool finds a power net and a ground net from its name (for example VCC, VDD, VBUS, GND), and gives the copper zones of each and the tracks of the power nets.

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

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.4/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 burden. It does disclose the key behavioral trait that detection is a name-based heuristic, warning the agent results may miss or misidentify nets, but it omits whether the tool is read-only, what happens when no power net is found, and whether multiple power nets are considered.

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?

It is short and front-loaded, leading with the deliverable. The second paragraph largely restates the first sentence (copper zones plus power-net tracks, plus the name heuristic) rather than adding information, which is mild redundancy.

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?

An output schema exists, so return structure need not be explained, and the heuristic caveat is present. However, for a tool with zero annotation coverage, the definition should say more about the read-only nature and behavior on boards without a recognizable power or ground net.

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 required parameter with 100% schema description coverage, so the schema already explains file_path as the .kicad_pcb file. The description adds nothing about the parameter, which is acceptable at this coverage level but not additive.

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 names a specific verb and resource: it returns copper zones and power-net routing for a board, and it states that power/ground nets are identified heuristically by name (VCC, VDD, VBUS, GND). That distinguishes it reasonably from the signal-integrity and generic net siblings, though it never names those alternatives.

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 only implied: the tool is for inspecting power distribution, but the description gives no explicit when-to-use condition, no prerequisites, and no routing to analyze_pcb_signal_integrity or analyze_pcb_nets. An agent can infer the context but not the boundaries.

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