Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_zone

Move a PCB zone by a relative offset in millimeters, using delta X and Y values.

Instructions

Shift a zone by a relative delta (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": {
      "zone_id": "<zone_id>",
      "delta_x_mm": "<delta_x_mm>",
      "delta_y_mm": "<delta_y_mm>"
    },
    "name": "move_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idYes
delta_x_mmYes
delta_y_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as immediate application, zone locking requirements, boundary checks, or side effects. It only states the basic action without contextual safety or constraint information.

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, efficient sentence with no redundant information. It is front-loaded with the verb and resource, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's simplicity (3 required parameters, no output schema), the description is somewhat adequate but lacks completeness. It does not mention prerequisites like zone existence or potential constraints such as grid snapping, leaving the agent with minimal behavioral context.

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%, but the description adds meaning by specifying that the delta is relative and in millimeters. However, it does not explain the zone_id parameter format or detailed semantics of delta values beyond the basic displacement concept.

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 states the action (shift) and resource (zone) with a specific relative delta and units (millimeters). It effectively distinguishes the tool from sibling move operations like move_footprint and move_shape by specifying 'zone' and 'relative delta'.

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 usage guidelines are provided. The description lacks any context on when to use this tool versus alternative move tools (e.g., move_footprint, move_shape) or any prerequisites, limitations, or exclusions.

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