Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_animation_track

Adds a track to an animation in a Godot AnimationPlayer, letting you target a node property or method so the animation can control it.

Instructions

Add a track to an animation in an AnimationPlayer.

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": {
      "node_path": "<node_path>",
      "animation_name": "<animation_name>",
      "target_path": "<target_path>"
    },
    "name": "add_animation_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationPlayer
track_typeNoTrack type (value, method, bezier, etc.)
target_pathYesNode path and property for the track
animation_nameYesAnimation to add the track to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it only implies a mutation. It does not say what happens if the animation or track already exists, whether track_type defaults to something, what errors occur on invalid paths, or whether the change is reversible.

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?

The single sentence is front-loaded and free of filler, with the resource and scope stated immediately. It is arguably terse for a four-parameter mutation tool, but no wording is wasted.

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?

For a mutation tool with no annotations and no output schema, the description is too thin. An agent still lacks knowledge of failure modes, defaults, and side effects, which the schema alone does not supply.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in the schema, establishing the baseline of 3. The description adds no further meaning about parameter interactions, such as how target_path relates to track_type.

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 description states a specific verb and resource — adding a track to an animation within an AnimationPlayer — so the action is unambiguous. It does not, however, differentiate itself from siblings like set_animation_keyframe or create_animation, leaving the agent to infer the boundary.

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?

There is no guidance on when to use this tool versus alternatives, nor on prerequisites such as whether the animation or AnimationPlayer must already exist. The agent can only infer usage from the tool name and schema.

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