Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_anim_bone_track_keys

DestructiveIdempotent

Replace or add per-key transforms for a bone track in a UAnimSequence, applying real pose data as one undoable step, then save the package.

Instructions

Replace the keys of one bone track of a UAnimSequence with the given per-key transforms (translation, rotation, scale: real pose data, not identity), adding the track when it is missing, through its data controller as one undo step, then save the package; num_keys_readback and first_key are read back from the data model. A bone_name the sequence's skeleton does not have is an error and nothing is written; an omitted bone_name targets the root bone. A failed save makes success false, with saved=false and save_error. Identity keys: add_anim_bone_track.

Returns: { anim_sequence_path, bone_name, num_keys, num_keys_readback, num_bone_tracks, first_key:{translation,rotation_euler}, success, saved, save_error, message }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysYesArray of per-key transforms: { translation:[x,y,z], rotation:[pitch,yaw,roll] (deg), scale:[x,y,z] }. translation default [0,0,0], rotation default [0,0,0], scale default [1,1,1].
bone_nameNoName of a bone of the skeleton of the sequence; omitted or empty means the root bone.
anim_sequence_pathYesAsset path of the UAnimSequence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedInput schema / properties / bone_name / description
      Previous value: -"Skeleton bone whose track to author (resolved/validated against the skeleton; first bone if empty)."New value: +"Name of a bone of the skeleton of the sequence; omitted or empty means the root bone."
  2. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: explains that the write goes through the data controller as one undo step, then saves the package, and that readback (num_keys_readback, first_key) comes from the data model. It also discloses the failure mode (saved=false, save_error) and the no-write-on-bad-bone behavior, which is exactly what a destructive mutation needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the core replace-and-save behavior leads, followed by error/return details. No output schema exists, so the explicit Returns block earns its space, though some clauses are packed tightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, saving mutation with no output schema, the description covers scope, undo/save semantics, error handling, and the return shape. Nothing an agent needs to invoke it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description still adds meaning by clarifying keys must be real pose data (not identity) and reiterating the root-bone default, which slightly exceeds what the schema alone conveys.

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

Purpose5/5

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

States a precise verb and resource: replace the keys of one bone track of a UAnimSequence with per-key transforms. It also distinguishes itself from the sibling add_anim_bone_track by noting the identity-key case, so an agent can route correctly.

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

Usage Guidelines4/5

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

Explains key context: the track is added when missing, an omitted bone_name targets the root bone, and an unknown bone name is a hard error. It points to add_anim_bone_track for identity keys, but doesn't fully frame when to prefer this over other track-editing tools.

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