Skip to main content
Glama
Sign In
pcb-mcp

pcb-mcp

by Amagtoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_footprints

Read-only

Retrieve all PCB footprints with positions, rotations, layers, and pad counts. Optionally filter by layer to view components on a specific side.

Instructions

Lists all footprints (components) on the PCB board with their positions, rotation angles, layers, and pad counts. Positions are in millimeters relative to the board origin. Y increases toward the bottom of the board (KiCAD convention). Optionally filter by layer name to see only components on a specific side. Valid layer values: F.Cu, B.Cu, In1.Cu, In2.Cu, F.SilkS, B.SilkS, Edge.Cuts. Use the returned reference designators (like U1, R1, C1) in follow-up tool calls that require a component reference.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_footprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_layerNoCanonical KiCAD layer name to filter footprints by. Common values: F.Cu (front copper), B.Cu (back copper), In1.Cu, In2.Cu (inner copper layers), F.SilkS, B.SilkS (silkscreen), Edge.Cuts (board outline). Omit to list footprints on all layers.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds concrete behavioral context: positions in millimeters relative to board origin, the KiCAD Y-axis convention, and valid layer names. This helps the agent anticipate output semantics without contradicting the annotations.

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 description is composed of four informative sentences, each adding value: the listing action, coordinate system, layer filtering, and follow-up usage. It is front-loaded and avoids redundancy with the schema, though slightly longer than strictly necessary.

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?

The tool has an output schema, so return format details are not required. The description covers the essential behavior, coordinates, layer filtering, and downstream usage, making it complete for a read-only listing tool.

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% – the filter_layer parameter's description already includes the valid layer values. The tool description does not add new meaning specific to the parameter beyond reinforcing the optional filter and the fact that omitting it lists all layers, so a baseline score of 3 is appropriate.

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?

The description opens with 'Lists all footprints (components) on the PCB board' – a specific verb and resource – and enumerates the exact attributes (positions, rotation angles, layers, pad counts). This clearly differentiates it from sibling tools like list_nets and list_tracks.

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

Usage Guidelines4/5

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

It provides context by stating the optional layer filter and lists valid layer values, plus explains how to use returned reference designators in follow-up tool calls. However, it does not explicitly state when not to use it or name an alternative like get_footprint for single-component details.

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

Deploy Server

Other Tools