Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rotate_shape

Rotate a shape by specifying an angle and center point to modify its orientation on the PCB layout.

Instructions

Rotate a shape by an angle around a center point (in degrees).

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>",
      "angle_deg": "<angle_deg>",
      "center_x_mm": "<center_x_mm>",
      "center_y_mm": "<center_y_mm>"
    },
    "name": "rotate_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
shape_idYes
angle_degYes
center_x_mmYes
center_y_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only states the action without disclosing behavioral traits like destructiveness, permissions, or effects on other objects. The word 'rotate' implies mutation but no further details.

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?

One concise sentence that immediately conveys the core purpose and key parameters. No filler or redundant information.

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 mutation tool with 4 required parameters, no output schema, and no annotations, the description is minimal. It lacks details on return values, side effects, prerequisites, or error conditions. The description is incomplete for safe usage.

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?

Schema description coverage is 0%, and the description adds minimal parameter semantics. It mentions 'angle' and 'center point' but does not elaborate on shape_id or units for each parameter. The schema names are partially self-explanatory but the description should compensate more.

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 (rotate), the resource (shape), and the parameters (angle, center point, units in degrees and mm). It distinguishes from siblings like move_shape or rotate_footprint by specifying center point and shape.

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?

The description provides no guidance on when to use this tool vs alternatives such as rotate_footprint or move_and_rotate_footprint. No exclusions or context are given.

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