Skip to main content
Glama

add_label

Add a local text label to a KiCad schematic at specified coordinates, with optional orientation and grid snapping for annotating connections or notes.

Instructions

Add a local label (text label) to the schematic.

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": {
      "file_path": "<file_path>",
      "text": "<text>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "add_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
textYesThe label text.
file_pathYesThe .kicad_sch file.
orientationNoThe angle of the label.
snap_to_gridNoTrue: move the label to the nearest point of the connection grid of the project (default 1.27 mm), except on a connection point of the sheet (a pin, a wire, a label).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a mutation of the .kicad_sch file but never says whether the change is written to disk immediately, whether it is undoable, or what happens when a label already exists at that position. Only the return-side burden is lifted by the presence of an output schema.

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?

A single front-loaded sentence with zero filler; nothing is redundant. It is terse rather than padded, so the shortfall is under-specification rather than verbosity.

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 six-parameter mutating tool with no annotations, one sentence is not enough: it omits coordinate units/coordinate space, whether the schematic file is rewritten, and how 'local' scope differs behaviorally from global/hierarchical labels. The output schema covers return values, but the call-side context an agent needs is missing.

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

Parameters3/5

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

Schema coverage is 67%, so text, file_path, orientation, and snap_to_grid are already documented. The description adds no meaning for any parameter, and x/y are left undescribed in both places with no unit convention given — baseline 3 reflects that the schema does most of the work but a real gap remains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Add a local label (text label) to the schematic') and parenthetical disambiguation clarifies that 'local' means a plain text label. The word 'local' implicitly contrasts with the sibling tools add_global_label and add_hierarchical_label, though no sibling is named explicitly.

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 choose a local label over a global or hierarchical label, which is the primary decision an agent faces given the three sibling label tools. No prerequisites (open project, active schematic) or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.