Skip to main content
Glama

animtree

Read-onlyIdempotent

Control and edit Godot AnimationTree at runtime: create nodes, add states and transitions, set blend parameters, play states, and modify properties for live adjustments.

Instructions

查询、控制和编辑 AnimationTree。支持创建节点、添加状态、添加转换、设置混合参数、播放状态、编辑状态属性。运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAnimationTree 节点名称(animtree_create 时使用)
valueNo参数值(float 用于 blends,{x,y} 用于 blend spaces)
actionYes操作类型:animtree_create 创建 AnimationTree 节点;animtree_add_state 添加状态;animtree_add_transition 添加转换;animtree_set_blend 设置混合参数;animtree_play 播放状态;animtree_state_edit 编辑状态属性
parentNo父节点路径(animtree_create 时使用,默认 root)
positionNo位置 {x, y}
to_stateNo目标状态名称(animtree_add_transition 时使用)
animationNo关联的 Animation 名称(animtree_add_state 时使用)
node_pathNoAnimationTree 节点路径
conditionsNo转换条件列表(animtree_add_transition 时使用)
from_stateNo源状态名称(animtree_add_transition 时使用)
state_nameNo状态名称
xfade_timeNo交叉淡入淡出时间(秒,animtree_add_transition 时使用)
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
load_autoloadsNo是否加载 Autoload 上下文(默认 true)
parameter_nameNo参数名称
tree_root_typeNo根节点类型(animtree_create 时使用,默认 AnimationNodeStateMachine)
animation_player_pathNoAnimationPlayer 的 NodePath(animtree_create 时使用)
Behavior1/5

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

Annotation contradiction: readOnlyHint=true conflicts with the description's mutation verbs (query, control, edit). The description also mentions runtime operation and current context, but this cannot override the severe inconsistency with the annotation. Thus transparency is minimal.

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?

The description is concise, front-loading the main purpose and breaking down capabilities in a structured list. It covers runtime scope and persistence guidance in a few sentences without extraneous detail.

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?

Given the tool's complexity (17 parameters, multiple actions) and absence of an output schema, the description gives a high-level overview but lacks per-action return details or error behavior. It is adequate for initial understanding but not fully complete.

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 schema has 100% parameter coverage with detailed descriptions. The tool's extra description does not add significant meaning beyond what the schema already provides for each parameter, so it stays at the baseline for high coverage.

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

Purpose5/5

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

The description clearly states the tool's purpose: query, control, and edit AnimationTree, listing specific operations like creating nodes, adding states, transitions, setting blends, and playing states. This goes beyond a generic verb+resource and provides enough specificity to distinguish from sibling animation-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states it is for runtime operations and advises editing .tscn for persistence, giving clear when-to-use and when-not-to-use guidance. It doesn't name sibling MCP tools, but the alternative approach is directly mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wgt19861219/godot-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server