Skip to main content
Glama

add_lake

Adds a freshwater lake inside a polygon on a Wonderdraft map, displaying only on land.

Instructions

Add a freshwater lake inside a polygon (only shows on land).

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. It does disclose one real behavioral trait — the lake renders only on land, so placement on water is silently ignored — but it says nothing about persistence, undo semantics, whether it mutates the current map, or what the call returns.

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?

One sentence, front-loaded with the action and resource, and the parenthetical constraint is placed where it is most needed. Nothing is redundant and nothing repeats the schema.

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

Completeness2/5

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

This is a mutation tool with no annotations and no output schema, yet the description never states that it modifies the map or what happens afterward. With a third of parameters undocumented, the description is too thin for the complexity of the operation.

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%, with just 'seed' documented. The description partly compensates by implying 'polygon' is the containment boundary for the lake, which the bare array-of-arrays schema does not convey. However, 'roughness' (default 0.3) has no meaning in either place, leaving an agent unable to reason about its effect.

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 ('Add a freshwater lake') plus a placement constraint ('inside a polygon'). An agent can distinguish this from add_river or add_territory by the word 'lake' alone, though the description does not explicitly name any sibling.

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 or when-not-to-use guidance beyond the geographic constraint '(only shows on land)'. It does not say whether to use add_lake versus paint_land or build_region, nor does it note prerequisites such as needing an existing map or polygon geometry.

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