Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_landscape

Create a flat landscape actor in Unreal Engine to import heightmaps without the editor's New Landscape dialog center/partial fill issues.

Instructions

Create a new terrain: spawn an ALandscape actor in the editor world sized by section_size x sections_per_component x component_count, filled with a FLAT heightmap at height. This is step 1 of two -- the relief comes from a following import_landscape_heightmap onto this actor, and going through this pair instead of the editor's New Landscape dialog is the point: the dialog treats its Location field as the terrain CENTRE (not the corner) and can fill only part of the components on import, silently. Verify the result with get_landscape_info (location, size_x/size_y, component_count), never with what you typed.

Returns: { actor_name: string, actor_path: string, section_size: int, subsection_size_quads: int, sections_per_component: int, component_count_x: int, component_count_y: int, quads_per_component: int, size_x: int, size_y: int, vertex_count: int, height_midpoint: int, imported: bool, landscape_created: bool, location: [number] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heightNoInitial uint16 height value, default 32768
locationNoOptional [x, y, z] world location
section_sizeNoVertices per section, default 63 (rounded up to power of two)
component_count_xNoComponents on X axis, default 8
component_count_yNoComponents on Y axis, default 8
sections_per_componentNo1 or 2 sections per component

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare write/non-idempotent/non-destructive, but the description adds real behavior the annotations can't: the heightmap is FLAT (no relief), the dialog's Location field means centre not corner, its import can silently fill only part of the components, and results must be verified rather than trusted. That is rich, non-redundant behavioral context.

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-loaded with the core action and the step-1-of-two framing, then rationale, then verification, then returns. It is dense and long, and the Returns enumeration is bulky, but no sentence is padding. Slightly less tight than a 5.

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?

For a moderately complex creation tool with 6 params and no output schema, the description supplies the missing pieces: a Returns enumeration, the follow-up step, and verification guidance. Nothing an agent needs to call it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the raw docs: it explains that height produces a FLAT fill and how section_size x sections_per_component x component_count combine to determine the actor's size, tying the parameters together functionally. The Returns block also clarifies what each derived size value means.

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 (create/spawn an ALandscape actor) plus the precise sizing algebra and the fact the heightmap is flat. It explicitly positions itself as 'step 1 of two' relative to import_landscape_heightmap, so an agent can distinguish it from siblings without opening a 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 alternative path explicitly (the editor's New Landscape dialog) and says why the pair of tools is preferred over it, plus the exact follow-up (import_landscape_heightmap) and the verification tool (get_landscape_info). This is explicit when/when-not plus alternatives guidance.

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