Skip to main content
Glama

unreal_create_widget_blueprint

Creates a UMG Widget Blueprint in Unreal Engine 5 for building UI layouts and widgets.

Instructions

Create a UMG 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_create_widget_blueprint"
  }
}

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 provided, so the description carries the full behavioral burden, and it discloses almost nothing: not where the asset is created, whether it is saved to disk, what permissions or editor context are required, or whether it collides with an existing asset. 'Create' implies a persistent mutation, but none of the consequences are described.

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?

The single sentence is front-loaded and free of filler, which is good. But it is undersized for a tool with a required opaque parameter object, so brevity comes at the cost of usability rather than from efficiency.

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?

The presence of an output schema relieves the description of explaining return values, and that is the only thing working in its favor. With no annotations and a completely undocumented required 'params' object, the definition leaves the agent unable to invoke the tool correctly.

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 is an untyped 'params' object with 0% schema description coverage and no declared properties, and the description adds no information about what keys it expects (name, path, parent class). An agent cannot construct a valid call from this definition alone.

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?

The description gives a specific verb ('Create') and resource ('UMG Widget Blueprint'), so an agent knows exactly what is produced. It does not, however, distinguish this from close siblings such as unreal_create_blueprint or unreal_create_animation_blueprint, which require inferring the difference from names alone.

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 versus unreal_create_blueprint or unreal_create_animation_blueprint, nor any stated preconditions (e.g., an asset path or parent class must exist first). The only signal is the tool name itself.

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