Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

remove_state_machine_state

Removes a specified state from an AnimationNodeStateMachine using the AnimationTree node path and state name, helping clean up unused animation states.

Instructions

Remove a state from 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>",
      "state_name": "<state_name>"
    },
    "name": "remove_state_machine_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationTree
state_nameYesState to remove

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 burden, and it only says 'remove'. It does not disclose whether removal is reversible, what happens to transitions attached to the removed state, or whether an error is raised for unknown state names.

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 wording, though it is arguably too terse for a destructive operation rather than padded.

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 no annotations and no output schema, the description omits important context: which AnimationTree/node_path is expected, side effects on connected transitions, and failure behavior. What is present is accurate but insufficient for confident invocation.

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%, so both parameters are already documented in the schema, and the description adds no extra meaning about formats or constraints. A baseline 3 is appropriate 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 gives a specific verb and resource ('Remove a state') and names the concrete container ('AnimationNodeStateMachine'), which pairs with sibling add_state_machine_state. It is clear what the tool does, though it does not explicitly contrast itself with the sibling.

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 prerequisites (e.g. the node must be an AnimationTree with a StateMachine root), and no pointer to list_state_machine_states for discovering valid state names. The agent must infer invocation context entirely from the tool name and schema.

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