Skip to main content
Glama

set_landscape_material

DestructiveIdempotent

Assign a landscape's render material by asset path; it propagates to all LandscapeStreamingProxy actors, so you don't manually update each proxy on World-Partition maps.

Instructions

Dress the terrain: assign the landscape's render material (and optionally its hole material) by asset path. Does MORE than the name suggests and that is the point -- it PROPAGATES to every LandscapeStreamingProxy, which is what actually renders on a World-Partition map, so you do not have to walk the proxies by hand. Consequence to budget for: it dirties one package per proxy plus the landscape. Idempotent (re-assigning the same material returns already_set), and the shader recompile is async even though the assignment is immediate. Do not trust material_assigned as the oracle -- re-read with get_landscape_material and spot-check a proxy's own landscape_material.

Returns: { landscape_name: string, material_path: string, material_assigned: bool, already_set: bool, hole_material_path?: string, hole_material_assigned?: bool, note: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
material_pathYesAsset path of the UMaterialInterface (e.g. "/Engine/EngineMaterials/WorldGridMaterial")
landscape_nameNoOptional landscape actor name, defaults to first found
hole_material_pathNoOptional asset path of the UMaterialInterface used for components with holes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond annotations: propagation to streaming proxies, one dirty package per proxy plus the landscape, idempotent behavior returning already_set, and async shader recompile despite immediate assignment. These are real consequences an agent must budget for.

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?

Front-loads the core action and then the propagation consequence, followed by the dirty-package warning and verification guidance. Slightly long and the em-dash aside is chatty, but every sentence carries useful information.

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?

Inline return shape documents outputs (landscape_name, material_assigned, already_set, hole fields, note), and the description covers propagation, dirtying, idempotency, and verification. Nothing an agent needs 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 the schema already documents material_path, landscape_name, and hole_material_path. The description confirms 'by asset path' and optional hole material but adds no syntax or format detail beyond the schema; 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?

States a specific verb+resource: 'assign the landscape's render material (and optionally its hole material) by asset path.' It also distinguishes itself from siblings by explaining it propagates to every LandscapeStreamingProxy, unlike mesh/actor material tools.

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

Usage Guidelines4/5

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

Explains why to use this over manually walking proxies, and routes verification to get_landscape_material ('Do not trust material_assigned as the oracle'). However, it does not give explicit when-not-to-use conditions or name a competing setter tool.

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