Skip to main content
Glama

list_pcb_footprints

Lists footprints on a KiCad PCB file, optionally filtered by layer, so you can inspect board components before further analysis.

Instructions

Give the footprints of a board.

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": "list_pcb_footprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesThe .kicad_pcb file.
filter_layerNoOptional layer of the footprints to give, for example "F.Cu" or "B.Cu". Empty: all footprints.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and largely drops it. It does not state that the operation is read-only, that it requires an existing board file, or how many footprints are returned or in what order; the only mitigating factor is that an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but it is terse to the point of under-specification rather than tight information design. There is no front-loaded structure beyond the bare statement of output.

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

Completeness2/5

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

For a two-parameter board-reading tool with no annotations, the description leaves out everything except the output noun. Because an output schema exists, return-value detail is not required, but the lack of any read-only or file-prerequisite context still leaves the definition thin.

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%, with both file_path and filter_layer documented including an example layer name and the "Empty: all footprints" default behavior. The description adds nothing beyond the schema, so the baseline 3 applies.

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

Purpose3/5

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

"Give the footprints of a board" names a resource (footprints) and a scope (of a board), which distinguishes it loosely from library-oriented siblings. But "give" is a weak verb and the phrasing does not make clear that this reads a specific .kicad_pcb file rather than searching a library, leaving the agent to infer the distinction.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites, and no reference to any alternative tool. An agent must infer from the name alone that this is the extraction path for board footprints versus the library-search path.

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