Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

list_state_machine_states

Lists all states in an AnimationNodeStateMachine from a given AnimationTree path, enabling inspection of animation state machine structure for Godot development.

Instructions

List all states in an AnimationNodeStateMachine.

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_state_machine_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationTree

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 disclosure burden, yet it says nothing about side effects, error behavior for an invalid node_path, or permissions. "List" weakly implies a read, but nothing confirms it or explains what happens if the path does not resolve to a state machine.

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 wasted words. It is arguably too terse rather than bloated, so it loses a point only for insufficient content, not verbosity.

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?

The tool is simple (one required string parameter, no nesting) and the schema documents it fully. However, with no output schema the description should hint at what the returned states look like (names, ids, positions), which it omits.

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%, with node_path already documented as "Path to the AnimationTree", so the baseline of 3 applies. The description adds no extra detail such as path format or whether the path must point at a state machine node specifically.

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?

Names a specific verb ("List") and resource ("states in an AnimationNodeStateMachine"), so the agent knows exactly what is enumerated. It does not distinguish itself from the sibling mutators (add_state_machine_state, remove_state_machine_state) or from list_animations, leaving that differentiation 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as add/remove_state_machine_state. The agent must infer that this is the read counterpart of the state-machine mutation tools.

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