Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_state_machine_transition

Connects two states in a Godot AnimationNodeStateMachine by adding a transition, so you can define source-to-destination state flow.

Instructions

Add a transition between two 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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "add_state_machine_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination state name
fromYesSource state name
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 and does very little with it. It does not say whether duplicate transitions are rejected, whether the call requires an open scene or editor context, whether the operation is reversible (remove counterpart), or what is returned on success or failure.

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, and the resource context is placed before the operation's target. It is efficient but so terse that it borders on under-specification rather than tight writing.

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 (three required string parameters), the schema is fully documented, and no output schema exists, so the bar is modest. Still, an agent lacks the preconditions and failure behavior needed to call this confidently in a state-machine construction sequence.

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 each of node_path, from, and to documented in the schema itself, so the baseline of 3 applies. The description adds only the conceptual framing that 'from' and 'to' are states within the state machine, without format or naming-convention detail beyond the schema.

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 ('Add a transition') and scopes it to an AnimationNodeStateMachine, which distinguishes it from the state-level sibling add_state_machine_state. It stops short of explicitly naming that sibling or contrasting the two, 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 when-to-use guidance, no stated preconditions (e.g., that the source and destination states must already exist), and no mention of alternatives such as add_state_machine_state for creating the states first. The agent must infer the workflow order entirely.

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