Skip to main content
Glama

unreal_add_widget

Adds a widget to a Widget Blueprint, enabling AI clients to construct or adjust Unreal Engine UI layouts through the editor bridge.

Instructions

Add a widget to a Widget Blueprint.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire burden, yet it discloses nothing beyond the bare action: not whether the Widget Blueprint must be open or compiled, whether a parent panel must be specified, what happens if the class is invalid, or whether the change is persisted. For a mutation tool with zero annotation coverage this is a substantial 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?

One front-loaded sentence with no filler, but it is too thin for a tool whose only parameter is an opaque object. Brevity here reflects under-specification rather than efficient structure.

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

Completeness2/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 the input side is entirely opaque and no prerequisites or behavioral constraints are given. An agent could not construct a valid 'params' payload from this definition alone.

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 single required parameter 'params' has an empty, undocumented object schema (0% coverage) and the description says nothing about what it must contain, such as widget class, parent panel, or instance name. With the schema contributing nothing, the description fails entirely to compensate.

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?

States a specific verb and resource and names the destination container ('Add a widget to a Widget Blueprint'), which distinguishes it from unreal_add_widget_to_viewport without the agent needing to open either schema. It stops short of naming that sibling explicitly, so the differentiation is inferable from the target noun rather than stated.

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 guidance on when to use this tool versus the sibling add_widget_to_viewport or create_widget_blueprint, and no stated preconditions such as the target Widget Blueprint needing to exist or be open. Usage is only implied by the tool name and one sentence of context.

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