Skip to main content
Glama

game_terrain

game_terrain

Create terrain meshes from heightmap data, modify terrain height with brush tools, and paint vertex colors for Godot environments.

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?

Annotations lack readOnlyHint and destructiveHint, and the description does not disclose whether operations are destructive, performance implications, or error conditions. Only says 'Create/modify', which is vague.

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

Conciseness4/5

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

A single sentence, no redundancy. Could include more structure but is efficient for the core purpose.

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?

With 13 parameters, multiple actions, no output schema, and no annotations, the description is too sparse. It does not explain return values, error handling, or how heightmap data is used, leaving many gaps.

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 100% and each parameter has a descriptive comment. The tool description adds no additional information beyond the schema, so baseline 3 applies.

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?

Description states 'Create/modify terrain meshes from heightmap data', which identifies the core action and resource. However, it omits the 'get_height' and 'paint' actions listed in the schema, so it is not fully comprehensive.

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, no prerequisites or exclusions mentioned. The sibling list is large but not referenced.

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/Fulviuus/godot-mcp'

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