Skip to main content
Glama

animation

Destructive

Query, control, and edit Godot motion assets. Handle playback, keyframes, tracks, and player states directly from the MCP server.

Instructions

查询、控制和编辑动画。查询: list_players, get_info, get_details, get_keyframes。播放: play, stop, seek, blend。编辑: create, delete, update_props, add_track, remove_track, add_keyframe, remove_keyframe, update_keyframe。运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNo方法参数
stepNo关键帧对齐步进值
timeNo关键帧时间(秒)
typeNoIK:IK 类型
limitNoIK:最大返回数量
speedNo播放速度,默认 1.0(blend)
valueNo关键帧值
actionYes操作类型
lengthNo动画长度(秒)
parentNoIK:父节点路径
updateNo跳转后立即更新节点(seek)
secondsNo跳转位置(秒)(seek)
from_endNo从末尾开始播放(play)
bone_nameNoIK:骨骼名
insert_atNo轨道插入位置,-1 为末尾(add_track)
loop_modeNo循环模式
node_pathNoAnimationPlayer 节点路径(除 list_players 外必填)
root_pathNo搜索起始节点路径(list_players)
blend_timeNo混合过渡时间(秒)(blend)
keep_stateNo停止时保持状态(stop)
propertiesNoIK:属性键值对
track_pathNo轨道路径,如 "Sprite2D:frame"(add_track)
track_typeNo轨道类型(add_track)
transitionNo过渡曲线,1.0=线性
method_nameNo方法名(method 轨道)
track_indexNo轨道索引
custom_blendNo自定义混合时间,-1 为默认(play)
custom_speedNo播放速度,默认 1.0(play)
library_nameNo动画库名称(create/delete)
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
animation_nameNo动画名称
keyframe_indexNo关键帧索引
load_autoloadsNo是否加载 Autoload 上下文(默认 true)
target_nodepathNoIK:目标节点路径
Behavior4/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false; the description adds important context that operations are runtime-only and non-persistent, and that persistence requires .tscn editing. It aligns with the annotations and also lists destructive actions like delete and remove.

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

Conciseness5/5

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

The description is compact and front-loaded, with a clear categorization of actions in three short sentences. Every sentence serves a purpose, and there is no redundant or filler content.

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?

This is a complex tool with 34 parameters and 21 actions, but no output schema. The description provides categories and runtime/persistence guidance, yet it omits the IK-related actions from the schema and does not explain return values or differences among query actions, leaving clear gaps.

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 description coverage, so the baseline is 3. The description groups actions but adds no per-parameter semantics beyond what the schema already provides, so there is no need to compensate.

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 clearly states the tool's purpose as querying, controlling, and editing animations, and enumerates specific action names grouped by category. It is more specific than the bare name 'animation', though it does not explicitly differentiate from the sibling tool 'animation_track'.

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 provides a clear breakdown of actions (query, playback, edit) and gives practical usage context: operations are runtime-only and affect only the current execution context, with persistence requiring .tscn editing. It does not explicitly mention alternative tools, but the persistence note serves as a meaningful exclusion.

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