Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_animation_tree_structure

Retrieve and inspect Godot AnimationTree structures to analyze animation state machines and debug node configurations.

Instructions

Inspect AnimationTree structure. (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": "get_animation_tree_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Inspect' suggests read-only behavior, the description fails to disclose what data structure is returned, the implications of 'autoConnect' and 'timeoutMs', or what makes this a 'compatibility' tool versus standard inspection methods.

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?

Extremely brief (effectively two fragments) and front-loaded with the core action. While efficiently worded, the extreme brevity contributes to under-specification given the lack of supporting metadata elsewhere.

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 zero schema descriptions, no annotations, no output schema, and numerous animation-related sibling tools, the description is insufficient. It fails to clarify the output format, the specific structure being inspected (nodes? states? transitions?), or how it differs from 'get_animation_info'.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters ('timeoutMs' and 'autoConnect'), yet the description provides no compensatory explanation of their semantics, valid ranges, or usage contexts beyond what the schema property names and types already convey.

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 ('Inspect') and resource ('AnimationTree structure'), distinguishing it from siblings like 'create_animation_tree' or 'set_tree_parameter'. However, the '(Compatibility tool)' parenthetical is cryptic and detracts slightly from clarity without explanation.

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 '(Compatibility tool)' note hints at a specific use case but provides no explicit guidance on when to use this versus alternatives like 'get_animation_info' or 'get_game_scene_tree', nor does it explain what 'compatibility' implies (deprecated? legacy format?).

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