Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_anim_bone_track

DestructiveIdempotent

Add an animation track for one skeleton bone to a UAnimSequence with identity keys, replacing existing keys in one undo step and saving the package.

Instructions

Add the animation track of one skeleton bone to a UAnimSequence through its data controller, filled with num_keys identity keys (zero translation, identity rotation, unit scale), as one undo step, then save the package. An existing track stays but its keys are replaced (idempotent). 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 missing sequence or skeleton is an error and a failed save makes success false, with saved=false and save_error. Real poses: set_anim_bone_track_keys; inverse: remove_anim_bone_track.

Returns: { anim_sequence_path, bone_name, num_bone_tracks, num_keys, success, saved, save_error, message }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_keysNoNumber of identity keys to write, rounded, minimum 1 (default 2); not checked against the frame count of the sequence.
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: -"Name of the skeleton bone"New value: +"Name of a bone of the skeleton of the sequence; omitted or empty means the root bone."
  2. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / num_keys / description
      Previous value: -"Number of identity keyframes to generate (default 2)"New value: +"Number of identity keys to write, rounded, minimum 1 (default 2); not checked against the frame count of the sequence."
  3. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover safety (destructive=true, idempotent=true), but the description adds substantial context beyond them: identity key values, single-undo-step semantics, package save, key-replacement behavior on an existing track, bone-not-found/missing-sequence errors, and the failure contract (saved=false, save_error). This is exactly the extra behavioral detail annotations cannot carry.

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?

Front-loaded with the core action, then behavior, then errors, then siblings. Dense but every sentence carries information; a minor amount of the param restatement overlaps the schema, keeping it from a 5.

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?

No output schema exists, yet the description enumerates the return fields and covers error and save-failure outcomes, idempotency, and the sibling relationship. Nothing an agent needs to call it correctly 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, but the description adds meaning the schema omits: it defines what an 'identity key' actually is (zero translation, identity rotation, unit scale) and reiterates the root-bone default. That definitional context earns above baseline.

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 specific verb (Add) and resource (the animation track of one skeleton bone to a UAnimSequence via its data controller), and explicitly names the siblings it is not: set_anim_bone_track_keys for real poses and remove_anim_bone_track as the inverse. An agent can distinguish this from all three related tools without opening a schema.

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?

Clearly routes the agent: 'Real poses: set_anim_bone_track_keys; inverse: remove_anim_bone_track', and explains the omitted-bone_name case targets the root. It does not state explicit exclusions beyond pointing to the real-pose alternative, so it falls just short of a full when/when-not spec.

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