Skip to main content
Glama
MalloyTheDev

Aseprite MCP

by MalloyTheDev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

import_reference_sequence

Import a sequence of images as per-frame references for rotoscoping, placing each on a dimmed, locked layer to overlay and draw animations.

Instructions

Import a sequence of images as per-frame references for rotoscoping.

Each image is placed on its own frame in a single dimmed, locked layer
(frames are created as needed). Draw your animation on a layer above, then
exclude this layer at export with ignore_layer="<layer_name>".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesYes
opacityNo
filenameYes
layer_nameNorotoscope
start_frameNo
scale_to_fitNo

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

Describes key behavioral traits: creates a dimmed, locked layer, frames created as needed, images per frame, export exclusion. No annotations provided, so description carries the burden; it covers the main behaviors but lacks details on side effects (e.g., overwriting).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences that are concise and front-loaded: first sentence states purpose, second sentence provides usage notes. No wasted words.

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?

Given the tool's complexity (6 params, no output schema, no annotations), the description covers the essential workflow. Missing details like image formats or behavior on existing frames, but still fairly complete for a common operation.

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%, and the description adds no explanation for the 6 parameters. Parameter names are self-explanatory, but the description does not clarify purpose or constraints beyond the name.

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 clearly states the tool's purpose: importing a sequence of images as per-frame references for rotoscoping. It uses specific verb+resource ('import... as per-frame references') and distinguishes from siblings like 'import_image' and 'add_reference_layer'.

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?

Provides clear guidance on how to use the tool: images placed on their own frames in a dimmed, locked layer, draw animation above, exclude at export. Does not explicitly list when not to use, but context is sufficient.

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

Install Server

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/MalloyTheDev/aseprite-mcp'

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