Skip to main content
Glama

add_settlement

Place a settlement symbol with an optional name label on a Wonderdraft map and return the symbol and label IDs for later editing.

Instructions

Place a settlement symbol and (optionally) its name label just below it. Returns [symbol_id, label_id]. Each kind has a curated default sprite (seed picks among its variants); set_key overrides the set and variant picks one sprite by index. scale multiplies the kind's default size.

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": {
      "name": "<name>",
      "pos": "<pos>",
      "kind": "<kind>"
    },
    "name": "add_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes
kindYes
nameYes
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
labelNo
scaleNo
set_keyNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclosure burden for a tool that mutates the map, yet it says nothing about whether the map must be open, permissions, whether the placement is undoable, or what happens on collision. It does disclose the return tuple and the determinism of seed, which is useful, but the mutation/undo/error profile is entirely absent.

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 dense sentences with no filler, front-loaded with the action and return value before parameter behavior. The parenthetical asides are compact, though the parameter-behavior sentence is somewhat crammed and would read better as a list.

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 an 8-parameter mutating tool with no annotations and no output schema, the definition covers sprite selection and return shape reasonably but omits coordinate semantics, map-open prerequisites, and failure modes. An agent could call it, but might easily pass a wrong pos format or call without an open map.

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 13% (only seed is documented in-schema), so the description must compensate, and it does explain set_key (overrides the set), variant (index into sprite variants), scale (multiplier on default size), label, and seed behavior. However, the critical pos parameter's coordinate convention (array of numbers) is never explained, and 'name' is left unqualified.

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 a settlement symbol and optionally its name label') and reveals the return value [symbol_id, label_id]. This implicitly separates it from add_symbol/add_label, but it never names those siblings, so the differentiation is left to inference.

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 implied by the kind enum (city, town, village, castle...) which makes clear this is the tool for settlement features. There is no explicit guidance on when to prefer add_settlement over add_symbol, nor any stated prerequisite such as an open map.

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