Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

auto_place_decoupling_cap

Place a decoupling capacitor and wire it to power and ground nets in a KiCad schematic, specifying position, value, reference, and net labels.

Instructions

Place a decoupling capacitor and wire it to power/ground nets.

Places the cap, wires pin 1 (top) to power_net and pin 2 (bottom)
to ground_net via stub wires + labels.

Args:
    lib_id: Cap symbol (e.g. "Device:C")
    reference: Reference (e.g. "C5")
    value: Cap value (e.g. "100nF")
    x: X position
    y: Y position
    power_net: Label for pin 1 (e.g. "VCC", "+3V3")
    ground_net: Label for pin 2 (e.g. "GND", "PGND")
    rotation: Rotation in degrees (default 0)
    symbol_lib_path: Path to .kicad_sym if using custom lib
    schematic_path: Path to .kicad_sch file
    project_path: Path to .kicad_pro file (for sub-sheet instance tracking)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lib_idYes
referenceYes
valueYes
xYes
yYes
power_netYes
ground_netYes
rotationNo
symbol_lib_pathNo
schematic_pathNo
project_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations provide only basic hints (non-read-only, non-destructive, non-idempotent). The description adds behavioral context by detailing the wiring method ('via stub wires + labels') but does not discuss potential side effects like overwriting existing components or net connectivity constraints.

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 one-line summary, followed by a paragraph and an Args list. It is relatively concise, though the Args list could be shortened since it partially repeats schema information. Still, 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?

Given the tool's complexity (11 parameters, 7 required) and the presence of an output schema, the description covers the operation thoroughly: placement, wiring details, pin assignments. It lacks prerequisites (e.g., schematic file must exist) but is sufficient for an agent to understand the core functionality.

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

Parameters4/5

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

With 0% schema description coverage, the description's Args section adds significant meaning beyond parameter names and types. It explains how each parameter is used (e.g., 'wires pin 1 to power_net', 'Cap value') and provides wiring details that are not in 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 starts with a clear verb+resource: 'Place a decoupling capacitor and wire it to power/ground nets.' It explicitly states the tool's specific function, which distinguishes it from siblings like 'place_component' or 'add_wires' that do not combine placement and wiring for decoupling caps.

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 usage for placement and wiring of decoupling capacitors but does not explicitly state when to use this tool versus alternatives like separate placement and wiring tools. No exclusions or alternative tool references are provided.

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