Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

upgrade_footprint_lib

Destructive

Upgrade a KiCad footprint library to the current format, using atomic writes and a backup for safe rollback.

Instructions

Upgrade a footprint library to current KiCad format.

Rewrites every footprint in the library, so this takes the library
directory.  kicad-cli has no per-footprint option here, and a single
.kicad_mod path is rejected.

KiCad performs the migration, as it should, but it performs it on a copy and
each result lands through the server's atomic write, so no footprint file can
be left truncated. Only files whose content actually changed are written, so
an upgrade that touches three footprints leaves the rest of the library
alone. The whole library is still copied to ``<name>.pretty.bak`` first and
the result names it, because that is the undo for an upgrade that SUCCEEDED.
There is exactly one, and every run overwrites it.

Each file is atomic; the library as a whole is not a transaction. An upgrade
interrupted midway leaves some footprints migrated and some not, and no file
damaged. Version control is still the better answer for a library you care
about.

Args:
    footprint_path: Path to a .pretty library directory.
        Optional; omit to use the configured default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
footprint_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description is exceptionally transparent about behavior: it rewrites every footprint, uses a copy with atomic writes, only writes changed files, creates a backup, and notes that the library is not a transaction. This goes well beyond the destructiveHint annotation, providing context about safety and side effects.

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 detailed but well-structured, with the purpose upfront and explanatory paragraphs. It is longer than minimal but every sentence adds valuable context about safety and behavior. It is concise relative to the complexity of the operation.

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 description covers all critical context for a destructive library operation: scope, backup, atomicity, partial failure, and alternatives. With an output schema present, no return-value details are needed. It is complete and leaves no major gaps for an agent to misuse the 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?

The description explains that footprint_path is a directory path and mentions a default, but it contradicts the schema which marks it as required (the description says 'Optional'). This inconsistency reduces clarity. Since schema coverage is 0%, the description needed to compensate but introduced a contradiction.

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 clearly states the action: 'Upgrade a footprint library to current KiCad format.' It specifies the verb (upgrade) and resource (footprint library), and distinguishes it from sibling tools like 'upgrade_symbol_lib' by explicitly mentioning footprint library.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: it takes a library directory, rejects a single .kicad_mod path, and advises version control as a better alternative for important libraries. It clearly explains when to use this tool and when not to.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProductOfAmerica/mcp-server-kicad'

If you have feedback or need assistance with the MCP directory API, please join our Discord server