Skip to main content
Glama

raise_area

Raise or lower land height inside a polygon by a specified amount; results clamp to 0–1 and water remains untouched.

Instructions

Raise (or lower, if negative) land height inside a polygon. amount is in land-height units: land height runs from 0 (sea level) to 1 (highest), so 0.1 raises by a tenth of the full range; results are clamped to 0-1. Water is untouched and never becomes 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>",
      "amount": "<amount>"
    },
    "name": "raise_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
polygonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 does disclose real behavior: negative values lower terrain, results are clamped to 0-1, and water is untouched and never converted to land. However, it omits whether changes are undoable, whether an open map is required, and what the call returns, leaving mutation-side effects partly unspecified.

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?

A single dense sentence-and-a-half, front-loaded with the action, then units, then edge behavior. Every clause adds information an agent needs and nothing is repeated from the schema or name.

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 two-parameter mutation tool with no annotations and no output schema, the amount semantics and side-effect notes are solid. Gaps around polygon format, prerequisites, and return behavior keep it from being complete for an agent to call this confidently without experimentation.

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?

At 0% schema coverage the description must compensate, and it does for amount: land-height units, 0-1 range, negative direction, and clamping are all spelled out. Polygon gets only the phrase 'inside a polygon' with no coordinate format, winding, or self-intersection expectations, so half the parameter set remains under-specified.

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?

Names a specific verb (raise/lower) and resource (land height inside a polygon), including the negative-amount direction. It is clear on its own, but it never distinguishes itself from nearby alternatives such as paint_land or add_mountain_range, which could plausibly also change terrain.

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, and no alternatives are named. The text explains unit semantics rather than the conditions under which an agent should pick this over a sibling terrain tool.

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