Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_track

Shift a board track by a given offset (delta) in millimeters along X and Y axes.

Instructions

Move a track 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": {
      "track_id": "<track_id>",
      "delta_x_mm": "<delta_x_mm>",
      "delta_y_mm": "<delta_y_mm>"
    },
    "name": "move_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes
delta_x_mmYes
delta_y_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

Only mentions 'relative delta', indicating movement type, but does not disclose side effects (e.g., connectivity impact), constraints (e.g., snapping), or undo behavior. With no annotations, description carries full burden and is insufficient.

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, no redundancy, directly states essential information. Every word earns its place.

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?

Adequate for a basic move operation but lacks details on return value, prerequisites (track existence), or coordinate system. Could be more complete given no output schema or annotations.

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

Parameters2/5

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

Adds unit context for delta parameters (millimeters) but does not describe track_id purpose. With 0% schema description coverage, description should compensate more but only partially does.

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?

Clearly states verb 'Move', resource 'track', and nature 'by a relative delta (in millimeters)'. Distinguishes from sibling tools that move different entities (e.g., move_footprint, move_shape).

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?

Implies usage for repositioning a track relatively, but provides no explicit when-to-use or alternatives. Lacks guidance on when not to use (e.g., for absolute positioning) or when to prefer other movement tools.

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