Skip to main content
Glama

list_libraries

List symbol or footprint libraries from KiCad global and project tables to see which libraries are available and which project entries override global ones.

Instructions

List the symbol or footprint libraries of KiCad and of a project.

The libraries come from the library tables: the global table of the installed KiCad version (with its nested tables), then the table of the project. When more than one row has the same library name, KiCad uses the last one: a project library replaces a global library.

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_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo"symbol" or "footprint".symbol
project_pathNoOptional .kicad_pro, .kicad_sch or .kicad_pcb file, or the project directory.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the lookup chain (global table of the installed KiCad version, including nested tables, then the project table) and the collision rule (last row wins, project overrides global). That is genuinely actionable behavior an agent could not infer from the schema. It stops short of stating what happens with an invalid project_path or whether KiCad must be installed.

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 the first sentence, followed by the supporting resolution rules. Every sentence contributes, with only minor redundancy in restating that libraries come from library tables.

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

Completeness4/5

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

For a two-optional-parameter read tool with an output schema, the description covers what is listed and how the two sources combine. No return-value explanation is needed given the output schema, so the remaining gap is minor (error behavior, whether KiCad must be installed).

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%, so both parameters are already documented, and the baseline is 3. The description adds only indirect meaning — that project_path selects the project table layered on top of the global tables — without explaining the accepted file/directory forms, which the schema already does.

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 description gives a specific verb and resource: listing symbol or footprint libraries belonging to KiCad and to a project. That distinguishes it from get_library_symbol/get_library_footprint (single-item retrieval) and from list_pcb_footprints (board contents), though it never names those alternatives explicitly.

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 only implied — an agent can infer this is the discovery step before get_library_symbol or add_component_from_library, but the description never says when to call it or when a sibling is the better choice. No exclusions or prerequisites are stated.

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