Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

list_animations

Retrieves all animations from a specified AnimationPlayer node path, helping you inspect available clips before editing or generating game code.

Instructions

List all animations 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>"
    },
    "name": "list_animations"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationPlayer node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and provides almost none: it does not confirm this is a read-only operation, does not say what happens if node_path is invalid or points at a different node type, and does not describe the shape of the result (animation names, lengths, track counts). Only the implicit 'List' hints at non-mutation.

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?

A single, front-loaded sentence with no filler; the scoping element is placed where it matters most. Nothing in it is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter list tool, so the bar is low, but with no output schema the description should at least indicate what is returned and how a missing/invalid node is handled. As written it is adequate to call but leaves return and failure behavior to guesswork.

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 coverage is 100% and the single parameter is already documented as 'Path to the AnimationPlayer node'. The description adds only the constraint that the target must be an AnimationPlayer, so it neither compensates for nor meaningfully extends the schema — the baseline of 3 applies.

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 (List), resource (animations), and a clear scope restriction (in an AnimationPlayer node), which separates it from mutation siblings like add_animation_track. It stops short of naming an alternative for finding or inspecting the node itself, so it is clear but not fully differentiated.

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 statement of when to use this over alternatives, no prerequisite that the node must already exist and be an AnimationPlayer, and no guidance such as using list_game_nodes_by_type to locate the node first. Usage is only inferable from the single sentence, which falls short of 'implied usage' guidance.

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