Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_shape

Move a shape in a PCB layout by a relative offset in millimeters, updating its position precisely.

Instructions

Move a shape by a relative offset (in millimeters).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shape_id": "<shape_id>",
      "delta_x_mm": "<delta_x_mm>",
      "delta_y_mm": "<delta_y_mm>"
    },
    "name": "move_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
shape_idYes
delta_x_mmYes
delta_y_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It specifies relative offset and units but omits details like coordinate system, cumulative moves, or side effects (e.g., snapping, undo). Minimal disclosure.

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?

Single sentence, zero filler, front-loaded with key information. Every word earns its place.

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?

Given no output schema and 0% parameter descriptions, the tool is simple but the description is insufficiently complete. Lacks details on coordinate system, constraints, and expected outcome, which are important for precise use.

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

Parameters3/5

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

Schema coverage is 0%, so the description adds some value by clarifying that delta_x_mm and delta_y_mm are relative offsets in millimeters. However, it doesn't explain shape_id or provide full param context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'move', the resource 'shape', and specifies it's a relative offset in millimeters. This distinguishes it from sibling tools like move_footprint or move_track, though it doesn't explicitly state it's for generic graphic shapes.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like move_footprint or rotate_shape. The description lacks context about shape types (e.g., graphic vs. footprint) and when not to use it.

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