Skip to main content
Glama
MalloyTheDev

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_reference_sequence

Import images as per-frame references for rotoscoping. Each image goes on its own frame in a dimmed, locked layer, letting you draw animation above and exclude it at export.

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, so `start_frame` may sit past the end). Draw your
animation on a layer above, then exclude this layer at export with
ignore_layer="<layer_name>".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesYes
opacityNoDefault: 128.
filenameYes
layer_nameNoDefault: "rotoscope".rotoscope
start_frameNoDefault: 1.
scale_to_fitNoDefault: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.10.0
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / images / title
      Removed value: -"Images"
    • addedInput schema / properties / layer_name / description
      Added value: +"Default: \"rotoscope\"."
    • removedInput schema / properties / layer_name / title
      Removed value: -"Layer Name"
    • addedInput schema / properties / opacity / description
      Added value: +"Default: 128."
    • removedInput schema / properties / opacity / title
      Removed value: -"Opacity"
    • addedInput schema / properties / scale_to_fit / description
      Added value: +"Default: false."
    • removedInput schema / properties / scale_to_fit / title
      Removed value: -"Scale To Fit"
    • addedInput schema / properties / start_frame / description
      Added value: +"Default: 1."
    • removedInput schema / properties / start_frame / title
      Removed value: -"Start Frame"
    • removedInput schema / title
      Removed value: -"import_reference_sequenceArguments"
  2. First observedv0.7.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=false (a mutation), and the description adds substantial side-effect context: each image goes on its own frame in a single dimmed, locked layer, frames are created as needed, and start_frame may extend past the current end. It does not cover error behavior or layer-name conflicts, but it is well beyond the annotation baseline.

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?

The description is front-loaded with the core purpose, then adds just enough behavioral and workflow detail in three compact sentences. Every sentence earns its place, and the backtick usage aids scanning.

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 six-parameter mutation tool with no output schema, the description covers purpose, side effects, and pipeline integration well. However, it omits required-parameter semantics for images and filename and does not describe the return value, leaving meaningful gaps for an agent invoking it.

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 coverage is 67%, but descriptions mostly repeat defaults. The tool description adds meaning for start_frame (frames are created as needed) and layer_name (usable for export exclusion), yet it leaves required parameters images and filename undocumented, and does not clarify opacity or scale_to_fit beyond their schema defaults.

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 gives a specific verb and resource ('Import a sequence of images') and scopes it to per-frame references for rotoscoping. It implicitly distinguishes from single-image siblings like import_image, but never names an alternative tool explicitly.

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?

It states the rotoscoping use case and outlines a workflow (draw animation above, exclude at export), which implies when to use it. However, it does not name or contrast alternatives such as import_image or add_reference_layer, nor does it state when not to use this tool.

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