Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

delete_animation

Deletes a specified animation from an AnimationPlayer node using its node path and animation name, enabling cleanup of unused animations in Godot.

Instructions

Delete an animation from an AnimationPlayer 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>",
      "animation_name": "<animation_name>"
    },
    "name": "delete_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationPlayer
animation_nameYesName of the animation to delete

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 provided, so the description carries the full burden of behavioral disclosure. It says deletion occurs but does not state that the operation is destructive or irreversible, what happens if the animation is missing, permission requirements, or what is returned.

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?

Single sentence, front-loaded with the action and target, with no redundant wording. Appropriate for a simple two-parameter tool.

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 destructive two-parameter tool with no annotations and no output schema, the description is too thin: it omits safety, failure behavior, and result expectations. The schema covers parameters, but behavioral completeness is lacking.

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 coverage is 100%, so node_path and animation_name are already documented in the schema. The description adds no format, constraints, or examples beyond the schema baseline.

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?

States a specific verb, "Delete," and resource, "animation," scoped to an AnimationPlayer node, making it distinguishable from create_animation and play_animation. It does not explicitly name alternatives, but the action is unambiguous.

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?

No guidance is given on when to use this versus create_animation, play_animation, or other deletion tools, and no prerequisites are stated, such as whether the animation must exist or whether the AnimationPlayer must be selected. Usage is only implied by the verb.

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