Skip to main content
Glama

check_library_links

Checks a KiCad project's links to symbol and footprint libraries and 3D models, using ERC/DRC to find missing or mismatched library items before PCB updates or exports.

Instructions

Check the links of a project to its symbol and footprint libraries and 3D models.

The tool uses the checks of KiCad: ERC for the symbols of the schematic (a library or a symbol that KiCad does not find, a symbol that is not equal to its library symbol) and DRC for the footprints of the board. It finds the footprints of the schematic as "Update PCB from Schematic" does, and the 3D models of the footprints as the STEP export does (KiCad does not check 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": {
      "project_path": "<project_path>"
    },
    "name": "check_library_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYesThe project: a .kicad_pro, .kicad_sch or .kicad_pcb file, or its 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 carries the full burden and mostly succeeds: it discloses the underlying mechanism (KiCad's ERC for symbols, DRC for footprints, schematic-to-board footprint resolution like 'Update PCB from Schematic', 3D models resolved like the STEP export) and flags that KiCad itself does not check 3D models. It does not state that the call is read-only or whether it is expensive/long-running on large projects.

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 and the remaining sentences spend their words on concrete behavior rather than filler. The parenthetical asides are dense but each one adds information an agent would not otherwise have.

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?

An output schema exists, so return values need not be described, and the one parameter is fully covered by the schema. What remains missing is minor: no note on whether the check is read-only, and no hint at cost on large projects. For a single-parameter audit tool this is close to sufficient.

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% and the single parameter is fully documented there, including the accepted file types. The description adds no meaning about project_path beyond what the schema already says, so the baseline 3 applies.

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 states a specific verb and resource: check the project's links to symbol libraries, footprint libraries, and 3D models. It even enumerates what a broken link looks like (library or symbol not found, symbol differing from its library version). It never names a sibling such as check_symbol_fields or get_drc_violations, so the agent must infer the boundary from scope alone.

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?

Use is only implied: a project-wide library integrity audit. There is no when-to-use, no prerequisites (e.g. must the project be loaded or closed), and no statement about how this differs from get_erc_violations or get_drc_violations, which the ERC/DRC framing here could easily be confused with.

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