Skip to main content
Glama

unreal_set_widget_property

Set a widget property value in Unreal Engine 5 projects so AI clients can update UI widget settings via the editor bridge.

Instructions

Set a widget property.

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_property"
  }
}

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 supplied, so the description carries the entire behavioral burden, yet it discloses nothing: not that this mutates editor state, not what happens when the property name or value is invalid, not whether changes are undoable or require a transaction, and not what the response contains.

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?

It is a single short sentence with no padding, but here brevity reflects under-specification rather than efficiency—there is no structure, no front-loaded scope, and no information beyond the tool name.

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?

An output schema exists so return values need not be explained, but for a mutation tool with zero annotation coverage and a completely undocumented parameter payload, the definition leaves every call-shaping detail unspecified.

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?

Schema coverage is 0% and the single required 'params' argument is declared as a bare object with no properties, types, or descriptions. The description adds nothing about what keys that object expects, so an agent has no way to construct a valid call from either source.

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 a widget property" restates the tool name almost verbatim, giving only the generic verb+resource. It never says what kind of property (color, position, size, text, brush, visibility) or what 'set' means for an arbitrary property, so it cannot be distinguished from the specific sibling setters such as unreal_set_widget_color or unreal_set_widget_text.

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 at all: nothing says whether this is the escape hatch for properties without a dedicated setter, whether it should be preferred over or avoided in favor of the many specific set_widget_* siblings, or what prerequisites (widget must exist in the tree, valid property name) apply.

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