Skip to main content
Glama

set_decal_color

DestructiveIdempotent

Set an editor-world ADecalActor's DecalColor by label, returning the resulting RGBA. Pass exactly four numbers; other lengths keep the current color.

Instructions

Set DecalColor on an editor-world ADecalActor found by label; it only shows if the decal material uses a Decal Color node. A color that is not a 4-number array is ignored (current color kept). No undo, dirty flag or save; returns the resulting r, g, b, a.

Returns: { actor_label: string, r: float, g: float, b: float, a: float }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNoArray of exactly 4 numbers [r, g, b, a], a linear color such as [1, 0.5, 0, 1]; missing or another length keeps the current DecalColor.
actor_labelYesLabel of the ADecalActor in the editor world.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / color / description
      Previous value: -"Optional [r, g, b, a] (default: keep current DecalColor)."New value: +"Array of exactly 4 numbers [r, g, b, a], a linear color such as [1, 0.5, 0, 1]; missing or another length keeps the current DecalColor."
    • changedInput schema / properties / color / type
      Previous value: -"string"New value: +"array"
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint=true, destructiveHint=true), the description discloses non-obvious behavior: no undo, no dirty flag, no save, and that a malformed (non-4-number) color is silently ignored with the current color kept. This is exactly the extra context the annotations can't convey.

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?

Three tight sentences: the action and effect precondition come first, then the input edge case, then persistence caveats and the return shape. No filler.

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?

With no output schema, the description supplies the return fields (actor_label, r, g, b, a), and it covers mutation side effects and invalid-input handling. An agent has everything needed to call it correctly.

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 both parameters are already documented with the same 4-number-array and label semantics. The description echoes the invalid-input handling but adds no syntax or format detail beyond the schema, so the 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?

The description states a specific verb and resource ('Set DecalColor on an editor-world ADecalActor') plus the lookup key ('found by label'), which cleanly distinguishes it from siblings like set_decal_material, set_decal_size, and set_decal_sort_order.

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?

It clearly gives the condition under which the call has a visible effect ('only shows if the decal material uses a Decal Color node'), which is real usage context. It doesn't explicitly name an alternative tool or state when-not-to-use, so it stops short of a 5.

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