Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_text_position

Move a text item in KiCad PCB layouts to new coordinates (top-left for text boxes). Provide text ID and X, Y in millimeters.

Instructions

Update the position of a text item (top-left for text boxes).

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": {
      "text_id": "<text_id>",
      "x_mm": "<x_mm>",
      "y_mm": "<y_mm>"
    },
    "name": "update_text_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_mmYes
y_mmYes
text_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Lacks annotation coverage. Description only notes top-left origin for text boxes but does not disclose behavior for invalid text_id, coordinate limits, or whether positions are absolute or relative. No information about side effects.

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 fluff. All words carry meaning. Front-loaded with action.

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?

For a simple 3-param no-output tool, the description is adequate but lacks error handling and return info. Could mention that it updates the position in place.

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 coverage is 0%. Description does not explain x_mm or y_mm beyond the top-left hint; units (mm) are implied but not confirmed. No elaboration on coordinate system or values.

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 the action (update), the resource (text item position), and adds a specific detail for text boxes (top-left origin). This distinguishes it from sibling tools like update_text_attributes or 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 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 (e.g., move_shape for moving shapes). No exclusions or prerequisites mentioned.

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