Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

remove_state_machine_state

Delete specific states from Godot state machines to refactor animation logic and optimize node hierarchies in game projects.

Instructions

Remove state machine state. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_state_machine_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Compatibility tool' but provides no details about what happens to connected transitions when a state is removed, whether the operation is reversible, or what the return value indicates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (four words plus a parenthetical), avoiding bloat, but this brevity becomes a liability given the lack of schema documentation and annotations. The first sentence restates the tool name (tautology), earning minimal value.

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?

Given the destructive nature of removal operations, the presence of undocumented generic parameters, and the lack of output schema or annotations, the description is incomplete. It fails to explain parameter semantics, side effects on state machine topology, or success/failure indicators.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for its two parameters (timeoutMs, autoConnect), which appear to be connection-level settings rather than domain-specific arguments. The description fails to explain what these parameters control or why they are relevant to state removal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the core action (remove) and resource (state machine state) clearly enough to distinguish it from siblings like add_state_machine_state and remove_state_machine_transition. However, the appended '(Compatibility tool)' qualifier is vague and creates ambiguity about whether this is the preferred method or a legacy fallback.

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 parenthetical '(Compatibility tool)' implies limited or specific use cases but fails to provide explicit guidance on when to use this versus alternatives, or what compatibility scenarios require it. No prerequisites or side effects are mentioned.

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