Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

List animation library

list_animation_library
Read-only

List the platform animation library: ready clips (idle, walk, run, …) made once on a reference skeleton. generate_three_d with operation=library-animation puts them on any model rigged by operation=rig or auto-rig (input_task_id = the rig job). Each clip has its id, names, duration in seconds and the rig type it fits. Read-only and free.

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": "list_animation_library"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds genuinely new context: the operation is 'free' (a cost signal the agent needs before deciding to call), and it enumerates what each returned clip carries. It does not discuss result size, ordering, or pagination.

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?

Four short sentences, front-loaded with the purpose before the workflow advice and the return-field summary. Every sentence carries information, though the workflow sentence is dense with operation names and slightly interrupts the definition of what the list contains.

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

Completeness4/5

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

With no output schema, the description compensates by naming the fields each clip exposes (id, names, duration in seconds, rig type), which is exactly what an agent needs before calling. Combined with the free/read-only note and the downstream chaining hint, only ordering and result-size behavior remain unstated.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The reference to input_task_id belongs to the sibling generate_three_d workflow, not to this tool's own inputs, so it adds workflow context rather than parameter meaning.

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

Purpose5/5

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

A specific verb plus resource ('List the platform animation library') immediately followed by what the resource contains ('ready clips (idle, walk, run, …) made once on a reference skeleton'). It also distinguishes this tool from the sibling that consumes the data by naming generate_three_d and its operation values.

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 explains the position of this tool in the workflow: list clips here, then apply them via generate_three_d with operation=library-animation on a model produced by operation=rig or auto-rig. That is clear chaining guidance, but it never explicitly states when NOT to call this tool or contrasts it with other listing/discovery tools in the family.

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

All iDos Games toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources