Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

add_symbol

Add a new symbol to a KiCad library with pins, reference prefix, and optional body graphics. Creates the library file if missing.

Instructions

Add a new symbol definition to a .kicad_sym library.

Creates a complete symbol with pins and body graphics.  If the library
file does not exist it will be created.

Args:
    name: Symbol name (e.g. "MP4572GQB-P", "TLV75733PDBVR")
    pins: Pin definitions — list of dicts, each with keys:
        number (str): pin number, e.g. "1"
        name (str): pin name, e.g. "VIN" ("~" for unnamed)
        type (str): electrical type — "input", "output", "bidirectional",
          "passive", "power_in", "power_out", "tri_state",
          "open_collector", "open_emitter", "unconnected", "free"
        x (float): X position in mm (default 0)
        y (float): Y position in mm (default 0)
        rotation (float): angle 0/90/180/270 (default 0)
        length (float): pin length in mm (default 2.54)
    reference_prefix: Reference prefix e.g. "U", "R", "C" (default "U")
    is_power: True for power symbols (default False)
    pin_names_offset: Pin name label offset in mm (default 0.508)
    in_bom: Include in BOM (default True)
    on_board: Place on board (default True)
    footprint: Default footprint e.g. "Package_SO:SOIC-8" (default "")
    datasheet: Datasheet URL (default "~")
    rectangles: Optional body rectangle(s) — list of dicts with keys:
        x1, y1, x2, y2 (float): corner coordinates in mm
        fill (str): "none", "background", or "outline" (default "background")
        If omitted, a rectangle is auto-computed from pin positions.
    symbol_lib_path: Path to .kicad_sym file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
pinsYes
reference_prefixNoU
is_powerNo
pin_names_offsetNo
in_bomNo
on_boardNo
footprintNo
datasheetNo~
rectanglesNo
symbol_lib_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations are minimal (only readOnlyHint=false), so the description carries the burden. It discloses that the library file is created if missing, and that a rectangle is auto-computed if not provided. It does not mention conflict behavior (e.g., duplicate symbol name), but overall provides good behavioral context.

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 well-structured: a brief purpose statement, a behavioral note, then a detailed parameter list. It is slightly long but appropriate for the tool's complexity. Every sentence adds value.

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 all inputs and key behaviors (file creation, auto-compute of rectangles). It does not mention return values, but an output schema exists. Considering the complexity, it is fairly complete.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description fully compensates by documenting all 11 parameters with details, types, defaults, and for 'pins', the exact structure with keys and examples. This adds significant value beyond the schema.

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 verb 'Add', the resource 'new symbol definition', and the context 'to a .kicad_sym library'. It also mentions creating a complete symbol with pins and body graphics, and behavior if library doesn't exist, which distinguishes it from siblings like add_lib_symbol.

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 description implies this tool is for creating new symbols from scratch by saying 'Add a new symbol definition' and mentions file creation, but it does not explicitly compare to sibling tools like add_lib_symbol or provide criteria for when to use this vs alternatives.

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