Skip to main content
Glama

spawn_decal_actor

Creates or reuses a DecalActor in the editor world and assigns an optional material and size.

Instructions

Spawns a DecalActor into the editor world. If material_path loads as a UMaterialInterface it is assigned to the UDecalComponent (SetDecalMaterial). Size may be a uniform number or an [x, y, z] half-extent applied to DecalSize (read back).

Returns: { actor_label: string, actor_name: string, reused: bool, decal_size_x: float, decal_size_y: float, decal_size_z: float, decal_material: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoOptional [x, y, z] world location (default 0,0,0).
rotationNoPREFERRED: the OBJECT {"roll":R,"pitch":P,"yaw":Y} (any subset, absent axes are 0). The ARRAY form below is [pitch, yaw, roll] -- its index 2 is ROLL, NOT yaw, which once put a PlayerStart on its side. Optional [pitch, yaw, roll] world rotation.
decal_sizeNoOptional [x, y, z] half-extent for DecalSize (default 128,256,256).
actor_labelYesLabel for the spawned (or re-used) ADecalActor.
material_pathNoOptional content path of a UMaterialInterface to assign to the decal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-read-only, non-destructive, non-idempotent), so the bar is lower, yet the description still adds real behavior: material_path is assigned only if it loads as a UMaterialInterface (SetDecalMaterial), size is interpreted then read back, and the concrete return field set is enumerated. The meaning of the 'reused' flag is not explained in prose, keeping it from a 5.

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 purpose, followed by conditional behavior and a compact Returns block that is genuinely useful given there is no output schema. Nearly zero waste, though the parenthetical '(read back)' and dual size phrasing are slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a moderate-complexity spawn tool with full schema coverage and annotations, the description covers purpose, parameter quirks, and return shape well enough to call it. The unexplained reuse semantics (when/why 'reused' is true) and absence of any when-to-use guidance are the remaining gaps.

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 3 baseline applies, but the description adds meaning the schema does not: decal_size 'may be a uniform number' in addition to the string [x, y, z] half-extent the schema declares, and it names the SetDecalMaterial assignment target for material_path.

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?

Specific verb + resource ('Spawns a DecalActor into the editor world') that clearly separates it from the set_decal_* mutation siblings. It states scope (editor world) and the two things it configures, but never explicitly names an alternative tool the way a 5 would.

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?

The description never says when to reach for this versus set_decal_material/set_decal_size on an existing decal, or versus the generic spawn_actor/spawn_blueprint_actor. No preconditions or exclusions are given; usage is left to be inferred from the purpose sentence.

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