Skip to main content
Glama

search_library_footprints

Find KiCad footprints by name, description, or tags, with optional library and project filtering. Returns ranked matches to help you choose the right footprint for a schematic or board.

Instructions

Search the footprints of the KiCad libraries by name, description and tags.

Each word of the query must be in the library ID ("Resistor_SMD:R_0603_1608Metric"), the description or the tags. The order is that of the footprint chooser of KiCad: an exact name first, then the best score. The first search reads all libraries (some seconds); then an index in the user cache directory is used until a library file changes.

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": {
      "query": "<query>"
    },
    "name": "search_library_footprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of results in the table.
queryYesWords to find, for example "0603 resistor".
libraryNoOptional name of one library to search (also when it is hidden).
project_pathNoOptional project (.kicad_pro, .kicad_sch, .kicad_pcb or its directory), to include its libraries.
include_hiddenNoAlso search libraries that are hidden in KiCad.

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?

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the exact-name-first ranking order, warns that the first search reads all libraries and takes "some seconds", and explains that a cached index in the user cache directory is reused until a library file changes. That latency and caching behavior is exactly the kind of operational context an agent needs. It stops short of describing return shape or pagination, though an output schema exists to cover that.

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?

Four sentences, front-loaded with the purpose, then matching rule, then ranking, then performance/caching — a logical progression with no filler. It is dense but every sentence carries information; only the parenthetical path example is arguably redundant given the schema's example query.

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 search tool with five fully documented parameters and an output schema, the description covers the remaining unknowns an agent would care about: query semantics, result ordering, first-call cost, and cache invalidation. Nothing material about invoking it correctly is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it clarifies that every query word must match the library ID, description, or tags, which is stronger than the schema's "Words to find" example. The phrase "also when it is hidden" for the library parameter reinforces the include_hidden/library distinction, giving extra semantics the schema only partially conveys.

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 a specific verb and resource: "Search the footprints of the KiCad libraries by name, description and tags." The resource word "footprints" cleanly separates it from the sibling search_library_symbols, so an agent can route between them without inspecting either schema.

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?

It explains the matching rule ("Each word of the query must be in the library ID, the description or the tags") and the ranking order, which is genuine usage guidance for how to construct a query. However, it never states when to prefer this over lookups like get_library_footprint or list_pcb_footprints, nor any when-not condition, so the search-vs-fetch decision is left implicit.

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