Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_animation

Creates a new animation in an AnimationPlayer node from a node path and animation name, with optional length, enabling AI-driven Godot animation setup.

Instructions

Create a new animation in 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": "create_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoAnimation length in seconds
node_pathYesPath to the AnimationPlayer
animation_nameYesName for the new animation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 behavioral burden, yet it says nothing about failure modes. It does not state what happens if animation_name already exists (overwrite vs. error), whether node_path must reference an existing AnimationPlayer, whether the created animation is returned, or whether length defaults when omitted.

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 repetition. It is efficient, though its brevity leaves little structure for the agent to work with beyond the core action.

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 zero annotations, no output schema, and no stated error or overwrite semantics, the description is too thin. An agent cannot tell how to handle an existing animation name or a missing player without trial and error.

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 all three parameters are already documented in the schema; the description adds only the loose framing that node_path points at an AnimationPlayer, which the schema already says. Baseline 3 applies when the schema does the heavy lifting.

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 ("Create a new animation") plus the container ("in an AnimationPlayer node"), so an agent knows exactly what gets produced. It does not distinguish itself from close siblings like create_animation_tree or add_animation_track, leaving that inference to the agent.

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 mention of "in an AnimationPlayer node" contextually implies the precondition that an AnimationPlayer exists, but there is no explicit when-to-use, when-not-to-use, or alternative recommendation (e.g., add_animation_track for adding tracks to an existing animation).

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