Skip to main content
Glama

unreal_create_blueprint

Create a Blueprint asset in Unreal Engine 5 so AI clients can generate reusable gameplay logic and actor behavior inside the editor.

Instructions

Create a Blueprint asset.

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_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.2/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 full behavioral burden, and it discloses almost nothing. It does not say what asset path the Blueprint lands in, whether an existing asset is overwritten, whether a parent class must be supplied, or what permissions the operation requires — all material for a mutating create operation.

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 short sentence is front-loaded and free of waste, so there is no verbosity problem. The issue is under-specification rather than bloat: the definition is minimal to the point of carrying no usable information beyond the tool name.

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 needn't be explained, but the tool remains a create/mutation operation with no annotations, no parameter documentation, and no statement of effect. For an agent to invoke a Blueprint creation correctly it would need asset naming, path, and parent-class context that is entirely absent.

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 an opaque nested object named "params" with 0% schema description coverage, and the description adds no field-level meaning whatsoever. With one undocumented required parameter, the schema and description together give the agent nothing to construct a valid call from.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Create a Blueprint asset"), so the basic action is unambiguous. However, it does nothing to separate this tool from sibling creators such as unreal_create_animation_blueprint, unreal_create_widget_blueprint, and unreal_create_blueprint_macro — an agent cannot tell which class of Blueprint this produces or when to pick this versus those.

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, no prerequisites, and no mention of any alternative. The agent is left to infer entirely from the tool name whether this is the right creator for a plain Blueprint versus a specialized one.

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