Skip to main content
Glama

smooth_landscape_in_box

Destructive

Soften terrain by applying a 3x3 box blur to heightmap vertices inside a world-space box over 1-5 iterations. Blends hard rims left by flattening or height-setting without adding relief.

Instructions

Soften terrain: run a 3x3 box blur over the heightmap inside a world-space box, 1 to 5 iterations. The finisher for the other two sculpt tools -- flatten_landscape_in_box and set_landscape_height_in_box leave a hard rim, and a couple of iterations here blends it. It only averages what is there; it cannot add relief.

Returns: { landscape_actor_name: string, iterations: int, applied: bool, vertices_smoothed: int, region_width: int, region_height: int, region: [int] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
centerNoOptional [x, y, z] box center (alternative to box_min/box_max)
extentNoOptional [x, y, z] box half-extents (alternative to box_min/box_max)
box_maxNoOptional [x, y, z] world-space box maximum
box_minNoOptional [x, y, z] world-space box minimum
iterationsNoNumber of smoothing iterations 1 to 5
landscape_actor_nameNoOptional landscape actor name, defaults to first found

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description reinforces this by explaining the operation is an averaging blur that 'only averages what is there; it cannot add relief.' That is genuinely useful behavioral context beyond the annotations, though it doesn't discuss permissions or performance cost.

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?

Three front-loaded sentences with zero waste, the algorithmic detail and sibling routing come first, followed by a compact Returns block. Every sentence earns its place.

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

Completeness5/5

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

There is no output schema, but the description supplies an explicit Returns shape (landscape_actor_name, applied, vertices_smoothed, region, etc.), so the agent knows what comes back. Combined with the annotations and the sibling routing, nothing needed to call it correctly is missing.

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 description coverage is 100%, so all six parameters are already documented. The description restates the iteration range (1-5) and the box concept but adds no new syntax or formatting guidance beyond what the schema provides. Baseline 3 is correct when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (3x3 box blur over the heightmap) plus scope (world-space box, 1-5 iterations), and explicitly names the two sibling tools it complements: flatten_landscape_in_box and set_landscape_height_in_box. An agent can distinguish it from those siblings without opening either schema.

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

Usage Guidelines5/5

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

Names the alternatives explicitly (flatten_landscape_in_box, set_landscape_height_in_box) and the condition that selects this tool: they 'leave a hard rim, and a couple of iterations here blends it.' Use-after relationship is unambiguous.

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

Deploy Server

Other Tools