Skip to main content
Glama
tureruygar-glitch

kicad10-mcp

place_near_pad

Place a component beside a target pad, outside the courtyard and aligned, to simplify decoupling capacitors, pull-ups, and series resistors.

Instructions

Place a part right next to a specific pad, just outside the target part's courtyard and aligned with the pad. Ideal for decoupling capacitors, pull-ups, and series resistors.

Args: reference: Footprint to move, e.g. 'C3'. target_reference: Part that owns the pad, e.g. 'U2'. target_pad: Pad number on the target, e.g. '13'. side: 'left', 'right', 'up', 'down', or 'auto' (the courtyard edge nearest the pad). gap_mm: Courtyard-to-courtyard gap in mm. angle_deg: Optional absolute rotation for the moved part (applied first). auto_orient: If the moved part has a pad on the target pad's net, turn it 180 degrees when that makes the same-net pad face the target (so the connecting track doesn't cross the part's other pad).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideNoauto
gap_mmNo
angle_degNo
referenceYes
target_padYes
auto_orientNo
target_referenceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It explains placement geometry and the conditional auto_orient 180-degree flip, but omits prerequisites (e.g., footprint lock state) and side effects (whether existing placement or routing is modified).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose statement, then usage guidance, then a structured Args block. No filler; every line earns its place and the most important information is first.

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 the description needn't explain return values. For a 7-parameter placement mutation it covers purpose, use cases, and all parameters, but leaves prior-state handling and error behavior unstated.

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?

Schema description coverage is 0%, so the description must define all 7 parameters. It does so fully: each arg is listed with meaning, examples, and allowed enum values for side; angle_deg and auto_orient behaviors are clarified beyond the schema defaults.

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?

States a specific verb (place) and resource (part next to a pad), and distinguishes from siblings like place_relative and move_footprint by pinning placement to a target pad with courtyard/gap semantics.

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

Usage Guidelines4/5

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

Names ideal use cases (decoupling capacitors, pull-ups, series resistors), giving clear context for when to use it. However, it does not name alternatives or state when not to use this tool, so it falls short of a 5.

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

Deploy Server

Other Tools