Skip to main content
Glama

unreal_set_widget_text

Sets the text displayed by a specified Unreal Engine widget, enabling AI-driven UI updates through the editor bridge.

Instructions

Set widget text.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 full behavioral burden, and it discloses nothing: not that this is a mutation, whether it requires a valid widget reference, whether changes are immediate/undoable, or what happens on invalid input. For a write tool with zero annotation coverage this is a serious gap.

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

Conciseness3/5

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

Two words is technically concise and front-loaded, but the brevity reflects under-specification rather than efficiency; there is no structure, no object identification, and nothing an agent can act on beyond the 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 needn't be explained, but the opaque untyped "params" container with zero coverage is the critical missing piece and it is left entirely undocumented. Combined with no annotations, an agent cannot reliably construct a call from this definition.

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?

There is one required parameter (a generic "params" object) with 0% schema description coverage and no enumerated or named properties, and the description says nothing about what goes inside it — widget id, text value, formatting flags are all unstated. With low coverage the description must compensate and it does not at all.

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 text" restates the tool name almost verbatim: a bare verb plus resource with no scope, target identification, or differentiating detail from siblings such as unreal_set_widget_color or unreal_set_widget_property. An agent knows only that some text-setting occurs, not what kind of text (label, caption, rich text) or on which widget.

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?

No when-to-use guidance, no mention of alternatives (e.g. unreal_set_widget_property for arbitrary properties), and no prerequisites such as the widget needing to exist first. The agent must infer everything from the name alone.

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