Skip to main content
Glama

unreal_get_animation_graph

Inspect animation graph nodes to reveal their structure, connections, and properties, helping you debug state machines and animation Blueprints.

Instructions

Inspect animation graph nodes.

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

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 supplied, so the description carries the full disclosure burden, and it says nothing about whether the call is read-only, whether it queries a live editor session, what it costs, or what an empty result looks like. It does not contradict anything, but it adds almost no behavioral context beyond the verb.

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?

A single short sentence with no filler, so nothing is wasted. However, the brevity stems from under-specification rather than disciplined editing, and there is no front-loaded detail beyond the bare purpose.

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 explained. Still, for a tool whose sole required argument is an undocumented object, the definition omits the one piece of information an agent cannot infer, making it incomplete for correct invocation.

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 tool requires a single opaque "params" object with no properties and 0% schema description coverage, so the description is the only possible source of meaning. It says nothing about what belongs in "params" (graph asset path, node filter, depth), leaving the agent unable to construct a valid call.

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?

"Inspect animation graph nodes" gives a read-style verb and a concrete resource, so the basic purpose is legible. It does not differentiate from closely named siblings such as unreal_get_animation_blueprint or unreal_get_animation_info, and "inspect" leaves the depth of the operation vague.

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

Usage Guidelines3/5

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

The only implied guidance is the word "Inspect," which suggests a read operation on animation graphs. There is no statement of when to prefer this over animation blueprint or animation info siblings, and no prerequisites or exclusions are given.

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