Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_animation_keyframe

Sets a keyframe value on a specified AnimationPlayer track at a given time to control animation properties in Godot.

Instructions

Set a keyframe value on an animation track.

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>",
      "animation_name": "<animation_name>",
      "track_index": "<track_index>",
      "time": "<time>",
      "value": "<value>"
    },
    "name": "set_animation_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesTime position in seconds
valueYesKeyframe value
node_pathYesPath to the AnimationPlayer
track_indexYesZero-based track index
animation_nameYesAnimation name

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 are supplied, so the description carries the full behavioral burden and largely drops it. It does not state whether an existing keyframe at that time is overwritten, whether a new keyframe is inserted, whether the track/animation must pre-exist, what happens on out-of-range track_index, or whether the change is undoable.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined density.

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?

For a five-required-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits overwrite semantics, prerequisite state, and failure conditions that an agent needs in order to invoke it correctly.

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?

Schema description coverage is 100%, so every parameter (time in seconds, zero-based track_index, node_path, animation_name, value) is already documented in the schema. The description adds no additional meaning, which is the expected baseline when the schema does the work.

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 uses a specific verb and resource ("Set a keyframe value on an animation track"), so an agent knows exactly what is being modified. It does not explicitly contrast with siblings like add_animation_track, but the object being written (a keyframe at a track index) is distinct enough to be actionable.

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 guidance on when to use this tool versus alternatives such as add_animation_track or create_animation, nor any preconditions (must the animation and track already exist?). Usage must be inferred entirely from the name.

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