Skip to main content
Glama

unreal_get_animation_blueprint

Retrieves animation blueprint information from an Unreal Engine 5 project so AI clients can inspect animation graphs and related setup.

Instructions

Get Animation Blueprint info.

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_get_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

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 bears the full burden of behavioral disclosure. The word 'Get' weakly implies a read-only retrieval, but nothing is said about required editor/PIE state, permissions, or whether the asset must be loaded — all of which matter for an Unreal tool.

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?

One short sentence with zero padding and the verb front-loaded, so there is no verbosity problem. The issue is under-specification rather than wordiness — nothing is wasted because almost nothing is there.

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 described. However, the entirely opaque required 'params' object is undocumented in both schema and description, leaving the single thing an agent must supply completely unexplained.

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 object literally titled 'Params' with 0% schema description coverage, and the description adds nothing about its contents. With low coverage the description is expected to compensate, and it does not, so 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.

Purpose3/5

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

It states a verb (get) and a resource (Animation Blueprint), so the broad intent is legible, but 'info' is undefined — it doesn't say whether that means the asset's parent class, graphs, variables, or state machine contents. Siblings such as unreal_get_animation_info, unreal_get_animation_graph, and unreal_get_blueprint make this ambiguity consequential; the description gives no basis for choosing among them.

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. An agent must guess whether this is the right entry point versus unreal_get_animation_info or unreal_get_animation_graph.

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