Skip to main content
Glama

add_symbol

Places a symbol from a selected asset set at specified map coordinates, with optional variant, scale, rotation, mirroring, and seed for repeatable placement.

Instructions

Place one symbol from a set (key from list_asset_sets) at pos [x, y]. variant picks a sprite by index, otherwise it is random. scale multiplies the set's base size (1 = the size Wonderdraft places it at). rotation is in degrees, clockwise.

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": {
      "set_key": "<set_key>",
      "pos": "<pos>"
    },
    "name": "add_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
scaleNo
mirrorNo
set_keyYes
variantNo
rotationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden and does disclose useful behavior: variant defers to random when omitted, scale is relative to the set's base size, rotation is clockwise degrees. However it says nothing about the map-mutation side effects — whether the symbol is saved, is undoable, is treated as a manipulable object by move_objects/remove_objects, or what happens with an invalid set_key.

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?

Four tight sentences, one per key parameter, front-loaded with the core action. No filler, though the formatting is terse to the point of being slightly clipped and the sentence ordering does not follow the schema's field order.

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 7-parameter mutation tool with no annotations and no output schema, the description covers most of the important semantics but omits mirror entirely and never addresses return value or post-placement effects on the map. Adequate but noticeably incomplete for a write operation.

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 coverage is only 14% (just seed), so the description must compensate, and it largely does: it explains set_key's source, pos's shape, variant's index-or-random behavior, scale's multiplicative meaning and rotation's units/direction. Gaps remain: mirror is never mentioned and pos coordinate origin/units are undefined.

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 and resource ('Place one symbol from a set ... at pos [x, y]') and names the sibling that supplies the set key (list_asset_sets). It does not explicitly contrast itself with scatter_symbols or the other add_* placement tools, so differentiation is only partial.

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: 'one symbol' versus the existence of a scatter_symbols sibling hints at single-placement use, and the dependency on list_asset_sets for set_key is implied. There is no explicit when-to-use, when-not, or prerequisite statement (e.g. that a map must be open).

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