Skip to main content
Glama

apply_operations

Apply a batch of edit operations to an Aseprite sprite in a single atomic process. Operations run in order and roll back on failure.

Instructions

Apply a list of edit operations to a sprite in one atomic, single-process batch.

Each operation is `{"op": "<name>", "args": {...}}`. Supported ops (v1):
add_layer, rename_layer, set_layer_visible, set_layer_opacity, remove_layer,
add_frame, duplicate_frame, set_frame_duration, add_tag, remove_tag, set_pixel,
draw_line, draw_rectangle, fill_rectangle, draw_ellipse, fill_ellipse, fill_layer,
clear_layer, add_slice, remove_slice, replace_color. Ops run **in order against the
same open sprite**, so later ops see earlier ones (e.g. add a layer then draw on it).

Atomic: if any op fails the whole batch is rolled back and nothing is saved; the
error names the failing op index. `dry_run=True` validates the op list and returns
the plan **without launching Aseprite** (shape checks only — runtime issues like a
missing layer surface on a real run).

Returns a `workflow_manifest.v1` (kind "batch") with a per-op `operations` list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
filenameYes
operationsYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses atomicity, rollback on failure, dry-run mode, operation ordering, and return type. Does not mention file saving behavior or side effects beyond failure scenario.

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?

Concise single paragraph, front-loaded with purpose, followed by structure, atomicity, dry-run, and return info. Every sentence adds value.

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 3-param tool with no output schema, description covers behavior well but misses details on filename parameter (e.g., path format) and return manifest structure. Good but not fully complete.

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%. Description explains operations array format and lists supported ops, adding value for that parameter. dry_run is briefly explained, but filename is not described. Overall partial compensation for missing schema descriptions.

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?

Description clearly states it applies a list of edit operations atomically, lists supported ops, and explains batch behavior. Distinct from sibling tools that perform single operations.

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?

Describes atomic batch behavior and dry-run validation, implying use when multiple operations need to be applied together or validated. Lacks explicit comparison to individual sibling tools or when not to use.

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