Skip to main content
Glama

unreal_create_animation_blueprint

Creates an Animation Blueprint asset in an Unreal Engine 5 project, letting AI clients generate the animation logic container that drives character and skeletal mesh behavior.

Instructions

Create an Animation 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_animation_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/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, yet it discloses nothing: no required editor context, no asset path or package naming rules, no statement about overwrite behavior if the asset exists, no permissions or connection requirements.

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?

The single sentence is short and front-loaded, but its brevity reflects under-specification rather than economy. There is no wasted wording, but there is also almost no content to structure.

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?

For an asset-creation tool with a mandatory opaque params object and zero schema coverage, the definition provides nothing an agent needs to invoke it correctly. The existence of an output schema removes only the need to describe return values, which does not offset the missing call requirements.

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?

Schema description coverage is 0% and the sole parameter is an opaque untyped "params" object with no properties documented. The description does not explain a single field of that object, so an agent has no basis for constructing a valid call.

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?

The description is "Create an Animation Blueprint." which merely restates the tool name and title in sentence form. It does name a verb and a resource, but adds no scope, asset-type detail, or distinguishing information relative to siblings such as unreal_create_animation_montage or unreal_create_blueprint.

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 alternatives. An agent cannot tell from this text when an Animation Blueprint is the right asset versus an Animation Montage or a plain Blueprint; it would have to rely on name matching 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