Skip to main content
Glama

check_schematic_pin_pad_mapping

Compares schematic symbol pins with footprint pads using KiCad netlist update rules to flag missing pads, unnumbered pins, missing footprints, and pads without nets.

Instructions

Compare the pins of each symbol of a schematic with the pads of its footprint.

The tool uses the netlist that "Update PCB from Schematic" gives pcbnew (kicad-cli of the installed KiCad), and the rules of that update. A pin number that no pad has, a pin with no number, and a symbol whose footprint KiCad does not find are errors. A pad with a number that no pin has gets no net: this is a warning. A symbol has the pins of the units that the schematic has. The pads come from the library footprints, as a new footprint on the board gets them. For a board that has the footprints, run_drc with the schematic parity compares the footprints of the board. For a library symbol and a footprint, use check_pin_pad_mapping. When the netlist job finds annotation errors (a duplicate reference can join two symbols in one component), the tool lists them.

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": {
      "schematic_path": "<schematic_path>"
    },
    "name": "check_schematic_pin_pad_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
referencesNoOptional references to check, for example ["U1", "J3"]. All symbols of the netlist if empty.
schematic_pathYesA schematic of the project (.kicad_sch). For a sub-sheet or an other top-level sheet, the tool uses the project.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 so well: it names the data source (the netlist produced by "Update PCB from Schematic" via the installed kicad-cli), classifies missing-pad-pin, number-less-pin and unresolved-footprint as errors, and a pad with no matching pin as a warning. It also discloses that pads come from library footprints and that annotation errors (duplicate references) are listed. It stops short of stating explicitly that the operation is read-only and does not modify the project, which keeps it just under a 5.

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?

Core comparison is front-loaded and every sentence carries behavioral information — error/warning taxonomy, data source, netlist caveats. The phrasing is occasionally clunky ("the tool uses the netlist that 'Update PCB from Schematic' gives pcbnew"), but nothing is redundant enough to cut outright.

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?

An output schema exists, so return-shape explanation is not required, and the description still supplies the severity semantics an agent needs to interpret results. For a two-parameter read/analysis tool with full schema coverage, nothing material is missing.

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 description coverage is 100% and both parameters (schematic_path, references) are already documented with defaults and examples, so the baseline is 3. The prose adds meaning about the domain (sub-sheets resolve to the project) but nothing about the parameters themselves beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb+resource: "Compare the pins of each symbol of a schematic with the pads of its footprint." It then distinguishes itself from the two most similar siblings by name — run_drc (uses the board's actual footprints) and check_pin_pad_mapping (library symbol + footprint). An agent can select it without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing is provided: use run_drc with schematic parity when a board already has footprints, and check_pin_pad_mapping for a library symbol/footprint pair. Both alternatives and the conditions that select them are stated, which is exactly the when-to-use/when-not-to-use guidance the dimension rewards.

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