Skip to main content
Glama

check_pin_pad_mapping

Compares symbol pin numbers with footprint pad numbers using KiCad's Update PCB from Schematic rules, flagging pins without pads as errors and pads without pins as warnings.

Instructions

Compare the pin numbers of a library symbol with the pad numbers of a footprint.

The tool uses the rules of "Update PCB from Schematic" of the installed KiCad. A pin number that no pad has, and a pin with no number, are errors. A pad with a number that no pin has gets no net: this is a warning. KiCad 10 reads a stacked pin number ("[1-4]") as more than one pad number. The check uses the pins of all units, for each body style.

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": {
      "symbol_lib_id": "<symbol_lib_id>"
    },
    "name": "check_pin_pad_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathNoOptional project (.kicad_pro, .kicad_sch, .kicad_pcb or its directory), to include its libraries.
symbol_lib_idYesThe library ID of the symbol, for example "Device:R".
footprint_lib_idNoOptional library ID of the footprint, for example "Resistor_SMD:R_0603_1608Metric". If empty, the tool uses the Footprint field of the symbol.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it defines the severity model (unmatched pin number or unnumbered pin = error; extra pad number = warning with no net), and notes KiCad 10 range syntax and that all units and body styles are checked. It omits that the operation is read-only/non-mutating and says nothing about how libraries are resolved when project_path is empty.

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 purpose is front-loaded in one sentence and the follow-on sentences each add rule detail rather than filler. The KiCad-10 stacked-pin aside is a slight detour but is genuinely relevant to interpreting results.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, one-required validation tool with an output schema and fully documented parameters, the description supplies the missing piece an agent needs: exactly what constitutes an error versus a warning. Nothing required to call or interpret the tool is absent.

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% and the schema already explains all three parameters, including the footprint fallback behavior. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies; the note about checking all units is scoping behavior rather than parameter semantics.

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 a specific verb and two specific resources (library symbol pin numbers vs footprint pad numbers), so the operation is unambiguous. It stops short of differentiating itself from the sibling check_schematic_pin_pad_mapping, leaving the agent to guess whether this operates on a library pair rather than a placed schematic component.

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 by the framing as a validation check mirroring 'Update PCB from Schematic', but there is no explicit when-to-use statement, no prerequisites, and no named alternative for the schematic-side variant. The error-vs-warning rules hint at what the tool is for without telling the agent when to reach for it.

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