Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_animation_tree

Creates and attaches an AnimationTree node to a specified parent node path, enabling animation blending and state control in Godot scenes.

Instructions

Create and attach an AnimationTree node.

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

Input Schema

NameRequiredDescriptionDefault
node_pathYesParent node path for 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 exist, so the description carries the full burden. 'Attach' signals that the scene tree is mutated, but the description says nothing about permission/scene-state requirements, whether the change is undoable or saved, what happens on an invalid node_path, or what is returned. For a mutating tool with zero structured safety metadata this is thin.

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?

One short sentence, front-loaded with the verb, with no wasted words. It is under-specified rather than bloated, but nothing in the text could be cut.

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?

With no annotations, no output schema, and a mutating create-and-attach action, the definition should say more about scene prerequisites and side effects. All an agent gets is the action and the fact that the node is attached somewhere under node_path.

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?

The single parameter has 100% schema description coverage ('Parent node path for the AnimationTree'), and the description adds no extra meaning such as whether the path is relative or absolute, whether the parent must be in the edited scene, or what happens if it already has an AnimationTree. With full schema coverage the baseline of 3 applies.

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?

A specific verb plus resource: 'Create and attach an AnimationTree node'. 'Attach' adds a second fact (it gets attached to the scene) beyond plain creation. It does not differentiate against nearby siblings such as add_node or set_animation_tree_root, but the resource noun is specific enough that an agent can tell what it makes.

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 statement of when to use this instead of add_node or create_animation, and no prerequisites (scene must be open, node_path must be an existing parent, whether an AnimationTree already exists on that node). The agent must infer the whole selection context.

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