Skip to main content
Glama

add_text

Place a text note on a schematic page or silkscreen layer at given coordinates as a single change, returning its name so you can edit or remove it later.

Instructions

Write text as ONE change. Without layer: a note on a schematic page (default Main) at (x, y) sheet units. With layer: board silkscreen at (x, y) mm, height default 1.5. The answer names it (G3 or silkscreentext:1) for edit_circuit set_drawing/remove_drawing. Other shapes: add_drawing.

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": "<file>",
      "text": "<text>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileYesCircuit file
pageNo
textYes
layerNo
heightNomm
fontSizeNo
rotationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses that units change by mode (sheet units vs mm), the default page (Main), the default height (1.5), and that the call returns a name usable by edit_circuit set_drawing/remove_drawing. It does not say what happens on name collisions or whether the change is undoable as a single group, leaving mutation semantics partly implicit.

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 text is front-loaded and telegraphic, with the mode split stated before the return-value detail. A few compressed phrases ("The answer names it (G3 or silkscreentext:1)") take a moment to parse but every sentence carries information.

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 9-parameter mutation tool with no annotations and no output schema, the description covers the core call path and return-value reuse well. It is still incomplete on the remaining parameters (fontSize, rotation, text/file) and on mutation side effects, which an agent would need to guess.

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 only 22%, so the description must compensate, and it does explain x/y semantics with mode-dependent units, page default, layer values mapping to silkscreen, and height units/default. It says nothing about text, file, fontSize, or rotation, leaving four parameters documented in neither place.

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 opens with a specific verb and resource ("Write text as ONE change") and then splits the behavior into two clearly named modes: a schematic page note versus board silkscreen. It explicitly redirects non-text shapes to add_drawing, so an agent can distinguish this tool from its sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete when-to-use branching: omit layer for a schematic note, supply layer for silkscreen, and use add_drawing for other shapes. It does not state any exclusion such as when text should be added via edit_circuit instead, but the mode-selection guidance is clear enough to act on.

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