Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_state_machine_state

Adds a named state to an AnimationNodeStateMachine within a Godot AnimationTree, optionally assigning an animation clip.

Instructions

Add a state to an AnimationNodeStateMachine inside an AnimationTree.

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

Input Schema

NameRequiredDescriptionDefault
animationNoAnimation clip to assign to the state
node_pathYesPath to the AnimationTree
state_nameYesName for the new state

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, yet it says nothing about what happens on duplicate state names, whether the animation clip must already exist, whether 'animation' is optional, how states are ordered, or what is returned. For a mutation tool this is a significant disclosure gap.

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 tight sentence with the target hierarchy front-loaded and no filler. It is brief to the point of terseness, but nothing is wasted.

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?

For a simple three-parameter tool with full schema coverage and no output schema, the description covers the core identity but omits prerequisites and failure behavior. Adequate as a minimum-viable definition, not complete for a mutation operation without annotations.

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, which sets the baseline of 3. The description adds no extra meaning about node_path format, state naming constraints, or the consequences of omitting 'animation'.

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?

States a specific verb ('Add') and a precise resource ('a state to an AnimationNodeStateMachine inside an AnimationTree'), so an agent knows exactly what is created and where. It does not explicitly name the sibling operations it differs from (add_state_machine_transition, remove_state_machine_state), but the resource granularity is clear enough to distinguish them.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. that the target AnimationTree must already contain a state machine), and no mention of the related transition/list/remove tools. Usage is only implied by the verb and target type.

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