Skip to main content
Glama

recolor_symbols

Repairs older or hand-edited Wonderdraft symbols by applying missing land-color tints and correcting default radius/offset values; optionally overwrite all tints or limit to specific symbol IDs.

Instructions

Repair symbols placed by older versions of this server (or by hand-edited files) so Wonderdraft draws them like its own: black-and-white "paintable" (sample_color) sprites get the land colour under them as their tint (only where it is missing, or for all of them with overwrite=true), and entries still holding the old wrong default radius 50 / offset (0, 0) get their sprite's own values. ids limits it to some symbols (default all). New placements never need this. Undoable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recolor_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 well: it discloses the two distinct repairs performed, that tinting is skipped where already present unless overwrite=true, that old default radius 50 / offset (0,0) values are the trigger, and that the operation is undoable. It does not say whether the map must subsequently be saved or what the call returns, which are the remaining gaps.

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 the purpose, then consequences, then parameters, then the undo note — a sensible order with no filler sentences. The nested parentheses and unusual quoting of "paintable" slightly slow parsing, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with no annotations and no output schema, the description covers what changes, when it applies, how to scope it, and that it is reversible. Only the post-call persistence step and return value are unaddressed.

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

Parameters4/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, and it does: 'ids limits it to some symbols (default all)' and overwrite toggles between filling only missing tints versus repainting all of them. It does not clarify the expected id string format, which is the one loose end.

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?

States a specific verb and resource: 'Repair symbols placed by older versions of this server' and explains exactly what is being corrected (tint colour, radius, offset) so Wonderdraft renders them natively. It also implicitly separates itself from the placement siblings (add_symbol, scatter_symbols) with 'New placements never need this.'

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?

Gives a clear when-not-to-use rule ('New placements never need this') and conditions the overwrite path on whether the tint is already present. It stops short of naming an alternative tool by name, but the repair-vs-create distinction is unambiguous from context.

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