Skip to main content
Glama

game_terrain

Create terrain meshes from heightmap arrays and modify them by adjusting height, painting vertex colors, or querying height at positions.

Instructions

Create/modify terrain meshes from heightmap data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position (for modify/get_height/paint)
zNoZ position (for modify/get_height/paint)
nameNoNode name
colorNoVertex color {r,g,b,a} (for paint)
depthNoTerrain depth in vertices
widthNoTerrain width in vertices
actionYesAction: create, modify, get_height, paint
radiusNoBrush radius (for modify/paint)
nodePathNoTerrain node path
maxHeightNoMaximum terrain height
heightDataNoArray of float height values (for create)
parentPathNoParent node path
heightDeltaNoHeight change amount (for modify)
Behavior2/5

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

With no annotations, the description carries full burden but only says 'create/modify terrain meshes'. It does not disclose side effects, destructive behavior, or requirements like existing nodes, making it insufficient for safe invocation.

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

Conciseness3/5

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

The description is concise (one sentence) but omits essential info like actions or parameter relationships. It is not wasteful but under-specified.

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?

The tool is complex (13 params, multiple actions, no output schema), yet the description fails to explain how to use it for each action or what results to expect. Missing critical context.

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?

The input schema has 100% description coverage, so the description adds minimal value beyond confirming heightmap data usage. Baseline 3 is appropriate.

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 clearly states the tool creates/modifies terrain meshes from heightmap data, using specific verbs and resource. It distinguishes from sibling tools that deal with other mesh types or game objects, though not 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 guidance on when to use this tool versus alternatives (e.g., other terrain or mesh tools). The description lacks any context for appropriate usage or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tugcantopaloglu/godot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server