Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_aligned_dimension

Add aligned dimension annotations to PCB layouts by specifying start and end points, height, and layer.

Instructions

Add an aligned dimension annotation to the board.

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": {
      "start_x_mm": "<start_x_mm>",
      "start_y_mm": "<start_y_mm>",
      "end_x_mm": "<end_x_mm>",
      "end_y_mm": "<end_y_mm>",
      "height_mm": "<height_mm>",
      "layer_name": "<layer_name>"
    },
    "name": "add_aligned_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_x_mmYes
end_y_mmYes
height_mmYes
layer_nameYes
start_x_mmYes
start_y_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 convey behavioral traits. It only states that it adds an annotation, but lacks details about transactions (e.g., need for begin_commit/push_commit), undoability, or effects on the board. This is insufficient for an interactive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. It efficiently communicates the tool's purpose, though it could benefit from additional behavioral context without becoming verbose.

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 the complexity (6 required parameters, no schema descriptions, no output schema), the description is too minimal. It does not explain what 'aligned' means, coordinate reference, layer significance, or commit requirements, leaving the agent underinformed.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters. It mentions none of the 6 required parameters (start/end coordinates, height, layer). The description adds no value beyond the schema property titles.

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 verb 'add' and the resource 'aligned dimension annotation to the board', making the tool's purpose immediately understandable. It distinguishes from sibling add_* tools which add shapes rather than dimension annotations.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, the description implies usage for adding dimensions, and there is no alternative add_dimension tool among siblings, so the context is clear enough.

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