Skip to main content
Glama

generate_landmass

Replace a Wonderdraft map’s entire terrain with generated continents, archipelagos, or islands; set coverage to control the land fraction and use a seed for repeatable layouts.

Instructions

Replace the whole map's terrain with generated land; coverage is the land fraction (0-1).

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": "generate_landmass"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNocontinent
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
coverageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavior: wholesale replacement of existing terrain. It does not say whether the operation is undoable, or whether dependent features (rivers, settlements, labels) survive the replacement — material gaps for a destructive bulk operation.

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?

A single compact sentence with the destructive action front-loaded and the parameter clarification trailing. No filler, though the semicolon clause could be its own short sentence for scanning.

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?

Covers the destructiveness and the most ambiguous parameter, which is decent for a 3-param, zero-required tool. But with no annotations and no output schema, the undefined 'kind' parameter and the lack of any irreversibility or undo note leave real holes.

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 33%; the description rescues 'coverage' by defining it as land fraction 0-1, and the seed semantics live in the schema. However the 'kind' enum (continent/archipelago/island) is never mentioned in either place, leaving a third of the parameters semantically empty.

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 scope: 'Replace the whole map's terrain with generated land.' The 'whole map' scope distinguishes it from the local sibling tools (paint_land, paint_ground, add_mountain_range) without naming them explicitly.

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

Usage Guidelines2/5

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

No when-to-use guidance and no alternatives named. An agent must infer that this is the wholesale-generation option versus incremental paint_* tools; there is no statement of preconditions or when this should be avoided.

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