Skip to main content
Glama

add_label

Adds a styled text label to a Wonderdraft map using theme presets, with control over color, size, rotation, and curve for clear place names and annotations.

Instructions

Add a text label using one of the theme's label presets (Town, City, Region, ...; preset_used says which one matched). color is "#rrggbb" or [r, g, b(, a)] floats 0-1 (0-255 values are rejected with a hint). size is the font size in px (default from the preset); rotation is in degrees, clockwise (90 = vertical); curve is Wonderdraft's label curve value stored as-is (0 = straight; non-zero bends the text along an arc, the sign picks the direction; start small and check in Wonderdraft, the preview draws it straight).

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": "<text>",
      "pos": "<pos>"
    },
    "name": "add_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes
sizeNo
textYes
colorNo
curveNo
presetNoTown
rotationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

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

With no annotations, the description carries the full burden; it covers value formats (color rejects 0-255 with a hint, size defaults from the preset, rotation is clockwise), which is genuinely useful context. It says nothing about persistence (whether save_map is required), coordinate units, or failure modes beyond color rejection. The 'preview draws it straight' note is a partial disclosure but leaves the core lifecycle undocumented.

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?

Front-loaded with purpose, then a dense per-parameter walkthrough with no filler sentences. The long parenthetical on curve is slightly run-on but every clause carries information the schema does not.

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?

Seven parameters, zero schema coverage, no annotations, and no output schema, so the description should do more: it never describes what is returned (preset_used is mentioned in passing, implying a response object but not naming it as an output), whether the label persists without save_map, or the coordinate system for the required pos. Adequate for value formats, insufficient for a mutation tool of this complexity.

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 0% and the description compensates well for five of seven parameters: color formats and rejection rule, size units and default source, rotation direction and orientation, curve semantics and sign, and preset names. However 'pos' (required) and 'text' are never explained -- notably the coordinate space for pos is left ambiguous -- so the compensation is strong but incomplete.

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?

Names a specific verb and resource ('Add a text label') and immediately scopes it to 'one of the theme's label presets (Town, City, Region, ...)', which distinguishes it from sibling adders like add_symbol or add_settlement. It stops short of an explicit sibling comparison, but an agent can tell what this creates.

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?

Usage is only implied: it is clear this is for text labels drawn from theme presets, but there is no statement about when to prefer add_label over add_settlement/add_territory, nor prerequisites such as whether a map must be open or changes saved. Parameter hints ('start small and check in Wonderdraft') are guidance but not tool-selection guidance.

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