Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

check_loop

Read-only

Detect whether an animation loops cleanly by comparing its last and first frames against in-loop steps. Returns a verdict (smooth, jump, duplicate, static, pingpong) and seam box for cropping.

Instructions

Check whether an animation loops cleanly: compares its last frame with its first against the steps inside the loop. verdict is smooth, jump, duplicate (the last frame repeats the first, which stutters), static, or pingpong, and seam_bbox says where a jump is, ready to crop with look. Compares up to 12 steps from long animations. Read-only. Headless: pass file.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
fileNo
to_frameNo
from_frameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the repeated 'Read-only' line earns nothing, but the description adds real behavioral context beyond them: the five possible verdict values with an explanation of the stutter case, the seam_bbox location output, and the sampling cap ('up to 12 steps from long animations') that tells the agent results are approximate on long clips.

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?

It is front-loaded with the core purpose and the verdict vocabulary, and every clause carries information (enum meanings, sampling limit, invocation mode). It is dense but not padded, though the trailing 'Read-only' sentence duplicates the annotation and could be dropped.

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?

With no output schema, the description does well to name the return fields verdict and seam_bbox and enumerate verdict values. However, for a four-parameter tool where three parameters are undocumented in both schema and description, and with no explicit differentiation from check_consistency, the definition is only partially complete.

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%, so the description must carry the burden for four parameters, and it only covers one ('pass ``file``' for headless mode). 'tag', 'to_frame', and 'from_frame' are never explained — an agent cannot tell whether the frame range narrows the compared loop segment or whether tag selects among multiple animations.

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?

The description uses a specific verb and resource ('Check whether an animation loops cleanly') and immediately explains the mechanism ('compares its last frame with its first against the steps inside the loop'). That mechanism distinguishes it from a sibling like check_consistency without the agent needing to open either schema.

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?

It gives a concrete operational condition ('Headless: pass ``file``') and routes the agent to the right follow-up tool ('ready to crop with ``look``'). It does not state when to prefer check_consistency or other checking tools, which is the only gap.

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