Skip to main content
Glama

unreal_set_animation_sequence

Assign montage or sequence references to Unreal Engine animation assets, enabling you to configure playback and montage behavior for actors and Blueprints.

Instructions

Set montage/sequence references.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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 burden, and it discloses nothing beyond the word "set": not whether existing references are overwritten, what permissions or editor context are required, or whether the change is persisted/undoable. Only the implied mutation semantics are conveyed.

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?

It is a single short clause with no filler and is front-loaded, but the brevity comes from under-specification rather than efficiency. It does not waste words, but it also does not earn its place by conveying anything actionable.

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 a mutation tool with an opaque untyped parameter object, no annotations, and no schema coverage, the description should at minimum explain the reference payload and side effects. The presence of an output schema only relieves the return-value burden, leaving the call contract entirely undocumented.

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?

There is a single required parameter named "params" typed only as an object, with 0% schema description coverage, and the description adds nothing about its shape or expected fields. The agent has no way to construct a valid call from either the schema or the description.

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?

"Set montage/sequence references" restates the tool name (unreal_set_animation_sequence) with only "references" added, which is itself undefined. It does not clarify what a "reference" is, what object it is attached to, or how this differs from siblings like unreal_set_sequence_duration or unreal_add_sequence_section.

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?

No when-to-use, prerequisites, or alternative guidance is given. An agent cannot tell from the description whether this binds a montage to a sequence, swaps an existing reference, or is required before unreal_render_sequence.

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