Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_animation_keyframe

Set specific keyframe values in Godot animations to control node properties at exact timestamps. Programmatically configure animation tracks via the MCP bridge for automated game development.

Instructions

Set keyframe value. (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": "set_animation_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. 'Set' implies mutation but lacks details on overwrite behavior, interpolation handling, or what 'Compatibility tool' means (deprecated? legacy?). No disclosure of side effects or requirements.

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 (4 words), which prevents verbosity. However, the parenthetical '(Compatibility tool)' consumes space without providing actionable information, representing wasted potential in an already minimal description.

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?

Animation keyframes are complex (requiring track identification, time, value, interpolation), yet the description offers no details on usage patterns. Combined with zero schema descriptions, no output schema, and no annotations, the description is insufficient for reliable agent operation.

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

Parameters1/5

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

Schema has 0% description coverage and includes additionalProperties: true, implying arbitrary key-value pairs are expected for the actual keyframe data (track, time, value). Description fails to document these expected properties or explain the purpose of timeoutMs/autoConnect, leaving parameters completely undocumented.

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

Purpose3/5

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

States the core action (set) and target (keyframe value), but '(Compatibility tool)' is unexplained and adds confusion. Does not clarify scope (e.g., which animation/track) or differentiate from siblings like add_animation_track beyond the implied verb.

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?

Provides no guidance on when to use this tool versus alternatives like add_animation_track or create_animation. No mention of prerequisites (e.g., existing animation/track) or when keyframes should be added vs modified.

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