Skip to main content
Glama

unreal_set_widget_position

Set the position of a UMG widget in an Unreal Engine 5 project, enabling AI clients to place or reposition UI elements on screen.

Instructions

Set widget position.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/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 burden, yet it discloses nothing about mutation effects, required widget state (must the widget be in a viewport?), permissions, or reversibility. Four words cannot characterize a mutation operation on a UI widget.

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 short to the point of being under-specified rather than concise; there is no waste, but there is also no information load. Brevity here is a defect, not an efficiency.

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 an opaque required params object and no annotations, the description is far too thin for an agent to call it correctly. Nothing about the parameter shape or behavior is recoverable from the 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?

The single parameter is a bare untyped 'params' object with 0% schema description coverage, and the description adds nothing — no coordinate units, no vector vs. scalar format, no required fields inside params. This is the worst case: the schema says nothing and the description says nothing.

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 position" is a verb+resource pair, but it is effectively a restatement of the tool name (unreal_set_widget_position) with no added scope, target, or coordinate-space detail. Siblings like unreal_set_widget_size or unreal_set_actor_location are only distinguished by the noun in the name, not by anything the description says.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use guidance, no preconditions, and no mention of alternatives such as unreal_set_widget_property or unreal_set_widget_size. An agent must guess whether this affects screen space, viewport, or local coordinates.

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