Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

look_animation

Read-only

Render a tag or frame range as one strip or grid image with each cell's frame number and duration, letting you inspect animation timing and poses.

Instructions

See an animation: returns a tag or frame range as one image, frames left to right and top to bottom. Defaults to every frame, capped at 64. A range of up to 6 frames is a strip and longer ones are a grid, unless columns is set. The result lists each cell's frame and duration. layer, scale, max_size, and background work as in look. 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": "look_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
fileNo
layerNo
scaleNo
columnsNo
max_sizeNo
to_frameNo
backgroundNochecker
from_frameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already declares this a safe read, and the description still adds real behavior: default range is every frame, hard cap of 64 frames, strip layout up to 6 frames and grid beyond that, and the result enumerates each cell's frame and duration. It omits cost/performance implications of large grids and any tag-vs-file exclusivity rule, which keeps it from a 5.

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?

Front-loaded with the return contract, then defaults, then layout rules, then parameter delegation — a logical order with no filler. The backticked ``look`` deferral is an efficient compression rather than padding, though the paragraph form makes the layout rules slightly harder to scan than a short list.

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?

For a nine-parameter, zero-schema-coverage tool with no output schema, the description does well on output shape (cells with frame and duration) and rendering limits, but leaves several parameters defined only by reference to another tool. An agent can invoke it plausibly with defaults, yet cannot confidently set `tag` vs `file`, `scale` units, or `from_frame`/`to_frame` semantics from this text alone.

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 description coverage is 0% across nine parameters, so the description carries the burden and only partially delivers: `columns` (layout override), `max_size` (via the 64-frame cap context), `file` (headless mode), and the frame range implied by "every frame" get coverage, while `layer`, `scale`, `max_size`, and `background` are deferred wholesale to "work as in ``look``". The tag/file relationship and from_frame/to_frame defaults and ordering are never explained.

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 opens with a specific verb and resource ("See an animation") and immediately clarifies the return shape: one image with frames laid out left-to-right, top-to-bottom. It differentiates itself from the sibling `look` by framing the output as an animation-wide composite and by delegating shared parameters to `look`, though it never states the contrast in so many words.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Headless: pass ``file``" is a concrete situational instruction, and "unless ``columns`` is set" gives conditional layout guidance. However, there is no explicit statement of when to choose this over `look` (single frame) or `export_animation` (file export), so the agent must infer the routing from the tool name and the composite-image framing.

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