Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_rvt_volume

Idempotent

Spawn an ARuntimeVirtualTextureVolume bound to an RVT asset so runtime virtual texture is produced in-scene; optionally fit its bounds to an actor like a landscape.

Instructions

Spawn an ARuntimeVirtualTextureVolume (the RVT producer that registers the runtime virtual texture into the scene and defines its world-space region) bound to an RVT asset. Without a volume, assign_rvt_to_landscape only wires the landscape as a writer -- nothing produces the RVT. Optionally fits the volume bounds to an actor (usually the landscape) in the same call. Headless-safe: spawns with a null VirtualTexture (no render-state) then binds a valid RVT. Idempotent: returns the existing volume if one already targets this RVT.

Returns: { volume_name, rvt_asset_path, bounds_aligned, bounds_align_actor?, already_existed }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoOptional [x,y,z] spawn location (default [0,0,0]; overridden by the bounds-align when bounds_align_actor is given).
volume_nameNoOptional. Actor label for the spawned volume.
rvt_asset_pathYesRequired. /Game path to the URuntimeVirtualTexture asset (create_rvt_asset).
bounds_align_actorNoOptional. Name/label of an actor (usually the ALandscape) to fit the volume bounds to; runs the engine "Set Bounds" after binding.

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 behavior beyond annotations: headless-safety (spawns with null VirtualTexture then binds), idempotent return-existing semantics, and the full return object shape. These are concrete operational traits an agent needs and are not derivable from the annotation hints alone.

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 purpose, then dependency context, then behavior, then returns. Dense but every sentence carries information; the Returns block is valuable given no output schema is defined.

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 spawning/mutation tool with annotations and no output schema, it covers purpose, dependency rationale, headless behavior, idempotency, and the return contract. Nothing an agent needs to invoke 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 coverage is 100%, so all four params are already documented, including the bounds_align_actor override of location. The description reinforces the bounds-fitting intent but adds little syntax or meaning beyond what the schema provides; baseline 3 applies.

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 (spawn an ARuntimeVirtualTextureVolume) and defines what that object does (registers the RVT into the scene and defines its world-space region). It also distinguishes from the sibling assign_rvt_to_landscape by explaining the producer/writer relationship.

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 clearly when this is needed: without a volume, assign_rvt_to_landscape only wires a writer and nothing produces the RVT. Gives the conditional context well, though it stops short of explicit 'do not use if' exclusions or naming a full alternative tool set.

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