Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

by ProductOfAmerica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_component

Move a placed component, turn it, or both.

Instructions

Move a placed component, turn it, or both.

The symbol and all its fields move together: each field keeps its place relative to the
symbol, rotation included, and keeps its own text angle, so KiCad draws it turning with
the symbol. KiCad's GUI would also re-place auto-placed fields after a turn when its
autoplace preference is on; this tool does not.

Wires, labels, junctions and no-connect flags stay where they are, as with KiCad's own
Move. The result lists every pin whose connections changed (what it left, what it now
meets); reconnect those with wire_pins_to_net or connect_pins.

x and y snap to the 1.27 mm grid when the symbol moves, and the grid point must lie on the
page. Passing the symbol's own position (as list_schematic_components reports it) turns it in
place without snapping, wherever it stands, off the page included. Nothing is written when
nothing would change.

Args:
    reference: Reference designator (e.g. "R1")
    x: New X position
    y: New Y position
    rotation: The absolute angle in degrees (None = keep current); a mirrored symbol keeps
        its mirror. It is written as KiCad writes it, so it also repairs an angle KiCad
        cannot load, such as 45, +90 or none; a call without it refuses one this tool
        cannot read as 0, 90, 180 or 270.
    schematic_path: Path to .kicad_sch file. Optional; omit to use the configured default.

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
rotationNo
referenceYes
schematic_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.1
    • changedInput schema / properties / rotation / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      0,
+      90,
+      180,
+      270
+    ],
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv0.9.1

TDQS

A4.8/5.0
Behavior5/5

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

It discloses behavior well beyond the annotations: fields move and rotate with the symbol, KiCad GUI autoplace is not replicated, wires/labels/junctions/no-connects stay put, and the result lists every pin whose connections changed. It also explains snapping rules, in-place rotation without snapping, and that nothing is written when nothing would change.

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?

It is front-loaded with the tool's purpose, then organized into behavior paragraphs followed by an Args section. Despite its length, every sentence carries useful behavioral or parameter detail warranted by the complexity and the lack of schema descriptions.

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

Completeness5/5

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

Given a mutation tool with annotations, five parameters, and an output schema, the description supplies all the missing context an agent needs: scope, side effects, snapping rules, rotation semantics, and follow-up actions. Nothing essential for correct invocation is absent.

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 carry parameter meaning, and it does: reference is a designator, x/y are new positions with detailed grid-snapping rules, rotation is absolute and None keeps the current angle, and schematic_path is optional with a configured default. The rotation explanation also covers mirrored symbols and invalid stored angles.

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 states a specific verb and resource: move or turn a placed component. The word 'placed' distinguishes this from siblings that add, remove, or place components, and the turn behavior is included up front.

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?

The description makes clear this is for moving/turning an existing component and tells the agent to reconnect changed pins with wire_pins_to_net or connect_pins. It does not explicitly compare against place_component or name when not to use this tool, so it stops short of a full when/when-not/alternatives guide.

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