Skip to main content
Glama

paint_land

Paints or erases land inside a polygon with a noise-displaced coastline, letting you shape natural terrain edges or straight borders in Wonderdraft maps.

Instructions

Paint (add) or erase (subtract) land inside a polygon [[x, y], ...] with a natural, noise-displaced coastline. roughness 0 gives straight edges.

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": {
      "polygon": "<polygon>"
    },
    "name": "paint_land"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoadd
seedNoRandom seed (0 to 2^32-1); the same seed gives the same result.
polygonYes
roughnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 behavioral burden, and it does disclose the meaningful trait that edges are noise-displaced and that roughness=0 yields straight edges. It omits what happens to underlying terrain when subtracting, whether the operation is undoable (an 'undo' sibling exists), and any auth/permission context, so the transparency is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the action and target, with the roughness edge case appended as a useful qualifier. No filler or restatement of the tool name.

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 four-parameter mutation tool with no output schema and no annotations, the description covers the action, the coordinate-pair format, the add/subtract duality, and the roughness behavior — enough to call it correctly. Remaining gaps (interaction with existing terrain, return value) are minor rather than blocking.

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 25% (only seed is documented inline), so the description must compensate. It does: it explains the polygon format, that mode means add vs subtract, and the concrete effect of roughness values — giving meaning to three of four parameters beyond the schema.

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?

The description gives a specific verb phrase ('paint (add) or erase (subtract) land') plus the resource and the geometric input shape ('inside a polygon [[x, y], ...]'). It does not name or contrast with any sibling (e.g. paint_ground, generate_landmass), so an agent must infer the boundary between land painting and ground/landmass generation.

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 through the add/subtract mode split, which tells the agent this is the tool for both placing and removing land. There is no explicit statement of when to prefer generate_landmass or paint_ground instead, and no prerequisites are mentioned.

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