Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_text_box

Add a text box to a PCB board with defined text, two corner coordinates, layer, and font size. Use for labeling or adding notes.

Instructions

Add a text box 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": {
      "value": "<value>",
      "x1_mm": "<x1_mm>",
      "y1_mm": "<y1_mm>",
      "x2_mm": "<x2_mm>",
      "y2_mm": "<y2_mm>"
    },
    "name": "add_text_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
x1_mmYes
x2_mmYes
y1_mmYes
y2_mmYes
size_mmNo
layer_nameNoF.SilkS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the operation without mentioning side effects (e.g., board modification, undo support), requirements, or constraints (e.g., coordinate system). This is insufficient for an agent to predict the tool's impact.

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 extremely concise (6 words), but every word adds value by identifying the verb and object. However, it could be slightly expanded to include minimal 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 tool's simplicity, the description lacks essential context (e.g., operates on the current board, text box properties like font or rotation). With no output schema and 7 parameters, the description is incomplete for reliable use.

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%, and the description does not explain any parameter (e.g., what 'value' represents, how coordinates define the text box). The agent gets no additional meaning beyond bare parameter names, which is inadequate for correct invocation.

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 ('Add') and the target resource ('a text box to the board'), making the tool's purpose immediately understandable and distinct from sibling tools like add_text or add_rectangle.

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 is provided on when to use this tool versus alternatives (e.g., add_text vs add_text_box). There is no mention of prerequisites or context (e.g., requires an open board), leaving the agent to infer usage from the name alone.

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