Aseprite Studio

Overview Schema Source Related Servers Discussions Admin

check_animation

Measure an animation without playing it: report per-frame bounds, ground row, centroid, height, repeated frames, color drift, and spacing to validate loop, one-shot, or scene animations.

Instructions

Measure an animation without playing it: per-frame bounds, ground row, centroid, height, repeated frames, colour drift and spacing. kind: "loop" (walk, idle: must close), "oneshot" (attack, hurt, death: may hold poses) or "scene" (several actors: report only).

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": {
      "path": "<path>"
    },
    "name": "check_animation"
  }
}

Input Schema

Name	Required	Default
`tag`	No
`kind`	No	loop
`path`	Yes
`layer`	No
`frames`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 'Without playing it' implies a non-destructive read and it discloses the report contents, which is useful. However, it never explicitly confirms read-only behavior, does not say whether it mutates state, and says nothing about failure modes (missing path, malformed animation).

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?

Dense and front-loaded: the core measurement list comes first, then the mode semantics. Every clause carries information, though the run-on enumeration of measurements sacrifices some scannability.

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

Completeness3/5

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

The measured output fields are well described, which compensates for the missing output schema. But with 0% schema coverage and no annotations, four of five parameters remain undocumented, and nothing is said about error behavior or what `path`/`layer`/`frames` should contain.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters. The description thoroughly explains `kind` and its three modes, but leaves `tag`, `path`, `layer`, and `frames` entirely undefined in both schema and description. Only one of five parameters is given meaning.

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 and resource ('Measure an animation without playing it') and enumerates the exact measurements produced (bounds, ground row, centroid, height, repeated frames, colour drift, spacing). It is clearly distinguishable from siblings like lint, compare, or find_glitches, though it never names those alternatives explicitly.

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 kind values carry real usage context: 'loop' for walk/idle that must close, 'oneshot' for attack/hurt/death that may hold poses, 'scene' for multiple actors where it only reports. That tells the agent which mode to pick, but there is no guidance on when to reach for check_animation versus lint, find_glitches, or compare.

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