Skip to main content
Glama

unreal_set_widget_color

Change an Unreal Engine widget's color by passing color parameters, so AI clients can update UI appearance during editor sessions.

Instructions

Set widget color.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_set_widget_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing. It does not say what color space or format is expected, whether the widget must already be in a viewport, whether the change requires a rebuild or is persistent, or what happens on invalid input. For a mutation tool this is a critical gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words is brief, but brevity here reflects under-specification rather than economy. There is no structure, no front-loaded constraint, and nothing that earns its place because nothing informative is said.

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

Completeness1/5

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

With no annotations, an undocumented nested params object, and no output schema detail conveyed in the description, the definition leaves an agent unable to invoke the tool correctly. The existence of an output schema removes only the need to explain return values; everything else is missing.

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

Parameters1/5

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

The schema exposes a single opaque "params" object with no documented properties and 0% description coverage. The description offers no field names, color representation, or value ranges to compensate, leaving the caller with no way to construct a valid request from the definition alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set widget color" restates the tool name almost verbatim and adds no scope, target selection, or distinguishing detail versus siblings like unreal_set_widget_property or unreal_set_widget_text. It does identify a verb (set) and a resource (widget color), so it is not misleading, but it is essentially a tautology.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must guess whether this targets a widget by name, path, or reference, and whether unreal_set_widget_property is the more general option. Nothing steers selection.

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