KiCad MCP Pro

Overview Schema Source Related Servers Discussions Admin

pcb_auto_place_by_schematic

Eliminate manual placement of PCB footprints. Use the current schematic and deterministic heuristics to position components automatically.

Instructions

Place PCB footprints from the current schematic using deterministic heuristics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pcb_auto_place_by_schematic"
  }
}

Input Schema

Name	Required	Default
`grid_mm`	No
`scale_x`	No
`scale_y`	No
`strategy`	No	cluster
`origin_x_mm`	No
`origin_y_mm`	No
`sync_missing`	No
`allow_open_board`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.2Aug 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With empty annotations, the description carries the full burden of behavioral disclosure. It mentions 'deterministic heuristics' but does not state whether existing placement is overwritten, whether a board must be open, or how missing footprints are handled. This leaves significant side-effect uncertainty.

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?

The description is a single, direct sentence with no filler or redundancy. It efficiently communicates the core purpose and key differentiator in minimal words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters, empty annotations, and significant side-effect potential, this one-line description is insufficient. It omits parameter meanings, preconditions, and behavioral consequences, even though an output schema exists.

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

Parameters1/5

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

Schema coverage is 0%, and the description does not explain any of the 8 parameters such as grid_mm, strategy, sync_missing, or allow_open_board. The phrase 'deterministic heuristics' adds no parameter-level meaning.

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 identifies the action (place), the resource (PCB footprints), the source (current schematic), and the method (deterministic heuristics). It distinguishes this tool from sibling auto-placement approaches like pcb_auto_place_force_directed.

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 use when a schematic is loaded and footprints need automatic placement, but it does not explicitly state when to prefer this over force-directed placement or manual placement. No alternatives or exclusions are mentioned.

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

Deploy Server