Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

play_animation

Plays a named animation on a specified AnimationPlayer node in Godot, enabling AI-driven scene animation control.

Instructions

Play an animation on an AnimationPlayer node.

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>"
    },
    "name": "play_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationPlayer
animation_nameYesName of the animation to play

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 supplied, so the description carries the full behavioral burden and does not meet it. It says nothing about whether playback blocks until completion, whether it restarts or queues if an animation is already playing, whether looping is honored, or what happens when the named animation is missing.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than deliberate economy.

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 playback trigger with no annotations and no output schema, the description should disclose at minimum sync/async behavior, restart semantics, and failure behavior. None of these are present, leaving the agent guessing about the tool's runtime traits.

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%, with both node_path and animation_name documented inline, so the schema does the heavy lifting. The description adds no meaning beyond the schema, which is the baseline expectation here.

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 gives a specific verb (play) plus the resource (animation) and names the target node type (AnimationPlayer), so an agent can distinguish it from create_animation, delete_animation, and add_animation_track by name. It stops short of explicitly naming a sibling, but the purpose is unambiguous.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is not told whether the animation must already exist, whether node_path is a scene-relative or absolute path, or what to do if playback is already running.

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