Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

upgrade_symbol_lib

Destructive

Upgrades KiCad symbol libraries to the current format safely. Migrates a copy atomically and creates a .bak backup, preventing truncation.

Instructions

Upgrade a symbol library to current KiCad format.

KiCad performs the migration, as it should, but it performs it on a copy:
the result lands through the server's atomic write, so your library is
replaced whole or not at all and can never be left truncated. A backup is
still taken beside it at ``<name>.kicad_sym.bak``, and the result names it,
because that is the undo for an upgrade that SUCCEEDED and is not something
an atomic write can offer. There is exactly one, and every run overwrites it.

Args:
    symbol_lib_path: Path to .kicad_sym file. Optional; omit to use the configured default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbol_lib_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description goes well beyond the destructiveHint annotation by explaining atomicity, the backup file behavior, that exactly one backup exists, and that every run overwrites it. This gives the agent a clear picture of the upgrade's 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 front-loaded with a clear purpose and uses a structured Args section. Though somewhat narrative, the extra details about atomicity and backup behavior are valuable and earned.

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?

The description covers key operational concerns: destructive behavior, atomic replacement, backup semantics, and the parameter's default. Since an output schema exists, it need not describe return values, and the missing guidance around when to use this tool is a minor gap.

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

Parameters2/5

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

The description adds meaning by identifying symbol_lib_path as a .kicad_sym file and mentioning a configured default. However, it states the parameter is optional while the input schema marks it required, creating a direct contradiction that could mislead an agent into omitting it.

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 first sentence clearly states the tool's action and target: 'Upgrade a symbol library to current KiCad format.' This is specific and distinguishes it from the sibling upgrade_footprint_lib, which targets a different resource type.

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?

The purpose statement implies when the tool should be used, but there is no explicit guidance about when to use it versus alternatives, nor any exclusions. The description focuses on behavior rather than usage context.

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