Skip to main content
Glama

set_animation_loop

Set the loop mode of a Godot animation by providing the library path, animation name, and numeric loop mode.

Instructions

Set the loop mode of an animation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anim_nameYes
loop_modeYes
library_pathYes
Install Server

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only says 'set the loop mode,' but does not explain what loop_mode number means, what happens if the animation doesn't exist, whether changes are persisted, or if there are side effects. This is insufficient for a mutation tool.

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 a single, front-loaded sentence with no filler. It is concise but under-specified, though conciseness in itself is fine.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three undocumented parameters, no annotations, and no output schema, the description is far too minimal to allow correct invocation. It lacks enum values for loop_mode, relationship between library_path and anim_name, and any error/return behavior.

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?

The input schema has three required parameters with no descriptions, and the description does not mention any of them or their semantics. The agent is left to guess what loop_mode numeric values are valid and how library_path relates to anim_name.

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 function: setting the loop mode of an animation. It uses a specific verb and resource, and no sibling tool shares this exact purpose, so it distinguishes itself. However, it lacks any additional scope or qualifiers, so a 5 isn't warranted.

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 like add_animation or set_keyframe, nor any prerequisites or context. The description is a bare statement with no usage conditions.

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

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/adityaairlangga12/lentera-godot-mcp'

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