Skip to main content
Glama

terrain

Create and modify Unity terrains: paint height and textures with brush, add trees and details, flatten, manage layers and rendering settings.

Instructions

Manage Unity Terrains. Actions:

  • create: Create a new terrain with specified size and resolution

  • get_info: Get terrain details (size, resolution, layers, trees, details)

  • set_height: Set terrain height at a world position with brush radius

  • get_height: Sample terrain height at a world position

  • flatten: Flatten entire terrain to a uniform height

  • set_detail: Paint detail/grass density at a position

  • paint_texture: Paint a terrain layer/texture at a position

  • add_tree: Add a tree instance at a normalized (0-1) position

  • get_layers: List all terrain layers (textures)

  • add_layer: Add a new terrain layer from a texture asset

  • set_settings: Modify terrain rendering settings

  • list: List all terrains in the scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoWorld X position or detail/alphamap X coordinate
zNoWorld Z position or detail/alphamap Z coordinate
layerNoTerrain layer index or detail layer index
scaleNoTree scale
widthNoTerrain width (create)
actionYesTerrain action to perform
heightNoTerrain height / max elevation (create/set_height/flatten)
lengthNoTerrain length (create)
radiusNoBrush radius
densityNoDetail density value
strengthNoPaint strength 0-1
tileSizeNoTexture tile size for add_layer
assetPathNoPath to save terrain data asset
layerPathNoPath to save the TerrainLayer asset
terrainIdNoInstance ID of the terrain
terrainNameNoName of the terrain GameObject
texturePathNoTexture asset path for add_layer
treeDistanceNoMax tree rendering distance
drawHeightmapNoEnable/disable heightmap rendering
prototypeIndexNoTree prototype index
basemapDistanceNoDistance for basemap rendering
drawTreesAndFoliageNoEnable/disable trees and foliage
heightmapPixelErrorNoHeightmap pixel error for LOD
heightmapResolutionNoHeightmap resolution (create, power of 2 + 1)
detailObjectDistanceNoMax detail object distance
treeBillboardDistanceNoDistance to switch trees to billboards
Behavior4/5

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

Each action has a one-line description that indicates its effect (e.g., 'flatten' says it flattens to uniform height). The readOnlyHint annotation is false, consistent with the mutating actions. However, deeper behavioral details (e.g., performance, undo support) are absent.

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?

The description is concise: a single introductory line followed by a bullet list of actions. Every sentence provides useful information with no redundancy.

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?

Given the complexity (26 parameters, 12 actions), the description lacks explicit mapping of parameters to actions. The schema partially compensates by noting which action a parameter applies to (e.g., 'width (create)'), but the description could be more complete.

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%, so the schema describes each parameter. The description adds no additional parameter semantics; it only lists actions. Baseline 3 is appropriate.

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?

The description clearly states 'Manage Unity Terrains' and lists 12 specific actions, each with a brief explanation. It distinguishes this tool from siblings as the only terrain-related tool among many.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives, but since no sibling tool handles terrain, usage is implied. There is no guidance on which action to choose 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/joel-wehr/unity-mcp'

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