Skip to main content
Glama

Animation Manage

animation_manage

Create and edit AnimationPlayers, animation libraries, tracks, and AnimationTree graphs—including state-machine transitions and blend-space points—to author Godot animations from an AI assistant.

Instructions

Animation authoring (players, libraries, tracks and AnimationTree graphs).

Ops: • tree_create(parent_path, player_path, name="AnimationTree", root_type="state_machine") Create an inactive AnimationTree linked to the player. root_type: state_machine|blend_tree|blend_space_1d|blend_space_2d. • tree_get(tree_path, graph_path="") Read graph nodes/points, properties, edges, triangles and tree parameters. • tree_node_add(tree_path, name, node_type="AnimationNodeAnimation", properties=None, position=None, graph_path="") Add a native node. position: {x,y}. State machines accept AnimationRootNodes. • tree_node_remove(tree_path, name, graph_path="") Remove a node and its edges. Undo restores identities, edges and parameters. • tree_node_set(tree_path, properties, graph_path="") Set editable properties of the selected graph node, e.g. animation or fadein_time. Configure variable input counts (0 to 256) at creation. This op preserves existing input topology. • tree_connect(tree_path, input_node, input_index, output_node, graph_path="") Connect a blend-tree input port. Occupied ports/outputs and cycles are refused. • tree_disconnect(tree_path, input_node, input_index, graph_path="") Disconnect a blend-tree input port. • tree_point_add(tree_path, name, position, node_type="AnimationNodeAnimation", properties=None, at_index=-1, graph_path="") Add a named blend-space point (native limit: 64). Names cannot contain '.' or '/'. position: number for 1D, {x,y} for 2D. at_index=-1 appends. • tree_point_set(tree_path, name, position, graph_path="") Move a blend-space point. Use tree_node_set at graph_path="Space/Point" for its properties. • tree_point_remove(tree_path, name, graph_path="") Remove a point. Undo restores its resource, name, index and manual triangles. • tree_transition_add(tree_path, from_state, to_state, graph_path="", properties=None) • tree_transition_set(tree_path, from_state, to_state, graph_path="", properties=None) • tree_transition_remove(tree_path, from_state, to_state, graph_path="") State-machine transitions. Properties include xfade_time, switch_mode, advance_mode, advance_condition and advance_expression. Start/End follow native restrictions.

Blend-space node properties include min_space, max_space, snap, labels, blend_mode, sync_mode and cyclic_length. 2D triangulation is automatic; a subsequent tree_get reads generated triangles after the editor updates them. Graph paths select nested resource names, e.g. "Locomotion/Blend"; empty selects tree_root. Graph writes are undoable and preserve shared resource identity. Enable a completed tree or set parameters with node_set_property (e.g. property="parameters/Blend/blend_amount").

• player_create(parent_path, name="AnimationPlayer") Create an AnimationPlayer with empty default library. • library_add(player_path, resource_path, library_name="") Attach a saved AnimationLibrary to an AnimationPlayer or AnimationTree. Undoable. Empty library_name selects the default library. Existing names/resources are refused. • library_remove(player_path, library_name="") Detach a library; clears autoplay if it points into that library. Undoable. • library_list(player_path) List library names, resource paths and clip names. Includes autoplay for AnimationPlayer. • delete(player_path, animation_name) Delete an animation clip from the default library. Undoable. • validate(player_path, animation_name) Check all track paths resolve. Returns broken_count + per-track issues. • add_property_track(player_path, animation_name, track_path, keyframes, interpolation="linear") Add a property track. track_path: "NodeName:property". keyframes: [{time, value, transition?}, ...]. interpolation: linear|nearest|cubic. • add_method_track(player_path, animation_name, target_node_path, keyframes) Add a method track. keyframes: [{time, method, args?}, ...]. • set_autoplay(player_path, animation_name="") Set autoplay. Empty animation_name clears. • play(player_path, animation_name="") Editor preview. Not saved with scene. • stop(player_path) Stop editor preview. Not saved with scene. • list(player_path) List animations with length, loop_mode, track_count, plus libraries and autoplay. • get(player_path, animation_name) Inspect a clip's tracks and keyframes in detail. • create_simple(player_path, name, tweens, length=None, loop_mode="none", overwrite=False) High-level: build a multi-track clip from tween specs in one call. tweens: [{target, property, from, to, duration, delay?, transition?}]. • preset_fade(player_path, target_path, mode="in", duration=0.5, animation_name="", overwrite=False) One-call fade-in/out (modulate.a). • preset_slide(player_path, target_path, direction="left", mode="in", distance=None, duration=0.4, animation_name="", overwrite=False) One-call slide-in/out (position). • preset_shake(player_path, target_path, intensity=None, duration=0.3, frequency=30.0, seed=0, animation_name="", overwrite=False) One-call shake (jittered position). • preset_pulse(player_path, target_path, from_scale=1.0, to_scale=1.1, duration=0.4, animation_name="", overwrite=False) One-call pulse / hover-bounce (3-keyframe scale ping-pong).

Preset target_path: accepts either a scene-absolute path (e.g. "/Main/World/Cube", matching every other scene tool) or a path relative to the AnimationPlayer's root_node (e.g. "World/Cube", matching how Animation tracks store node paths). Scene-absolute targets outside the player's root_node subtree are converted to a ..-prefixed track path via root_node.get_path_to(target), the same shape the relative form already accepts.

Canonical call shape: {"op": "<verb>", "params": {...}}. Flat op parameters are accepted as a compatibility alias when the client transmits them; op and session_id remain top-level.

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": {
      "op": "<op>"
    },
    "name": "animation_manage"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYes
paramsNo
session_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.4.1
    • changedInput schema / properties / op / enum
      Previous value: -[
      -  "add_method_track",
      -  "add_property_track",
      -  "create_simple",
      -  "delete",
      -  "get",
      -  "list",
      -  "play",
      -  "player_create",
      -  "preset_fade",
      -  "preset_pulse",
      -  "preset_shake",
      -  "preset_slide",
      -  "set_autoplay",
      -  "stop",
      -  "validate"
      -]New value: +[
      +  "add_method_track",
      +  "add_property_track",
      +  "create_simple",
      +  "delete",
      +  "get",
      +  "library_add",
      +  "library_list",
      +  "library_remove",
      +  "list",
      +  "play",
      +  "player_create",
      +  "preset_fade",
      +  "preset_pulse",
      +  "preset_shake",
      +  "preset_slide",
      +  "set_autoplay",
      +  "stop",
      +  "tree_connect",
      +  "tree_create",
      +  "tree_disconnect",
      +  "tree_get",
      +  "tree_node_add",
      +  "tree_node_remove",
      +  "tree_node_set",
      +  "tree_point_add",
      +  "tree_point_remove",
      +  "tree_point_set",
      +  "tree_transition_add",
      +  "tree_transition_remove",
      +  "tree_transition_set",
      +  "validate"
      +]
  2. Addedv3.1.4
  3. Removedv3.0.7
  4. First observedv2.9.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it repeatedly discloses undoability, refusal rules for occupied ports/cycles/existing libraries, identity preservation for shared resources, native limits like 64 points, and that play/stop are editor previews not saved with the scene. These are exactly the mutation and side-effect details an agent needs.

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

Conciseness5/5

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

The description is long but proportionate to a 31-operation dispatcher, and it is front-loaded with the tool's scope before the op catalog. Each bullet documents a distinct operation or constraint, and the final canonical call-shape note is essential compatibility information rather than filler.

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?

Given the tool's complexity and the 0%-covered input schema, the description supplies the operation semantics, parameter formats, mutation behavior, and constraints needed to invoke it correctly. Return-value explanation is not required because an output schema exists.

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

Parameters5/5

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

Schema description coverage is 0% and params is an untyped object, so the description must define operation parameters itself. It does so comprehensively, listing per-op parameter names, defaults, enums, coordinate shapes, keyframe schemas, and special cases like graph_path selection and preset target_path handling.

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

Purpose4/5

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

The opening states a specific domain: 'Animation authoring (players, libraries, tracks and AnimationTree graphs)', and the op catalog makes the tool's scope concrete. It does not explicitly distinguish this tool from the sibling animation_create, so sibling differentiation is the only gap.

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?

The description provides clear context for individual operations and explicit alternatives in places, such as using tree_node_set for point properties at graph_path="Space/Point" and node_set_property for enabling trees or setting parameters. It does not say when to choose this tool over animation_create, but usage within the tool's operations is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.