Skip to main content
Glama
ZeroTian

Aseprite MCP Tools

by ZeroTian

create_cel

Create an empty cel on a specific layer and frame in an Aseprite file, positioned at given x and y coordinates.

Instructions

Create an empty cel on a layer/frame.

Args: filename: Name of the Aseprite file to modify layer_name: Layer name to target frame_index: Frame index starting at 1 x: X position in pixels y: Y position in pixels

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
layer_nameYes
frame_indexYes
xNo
yNo
Behavior2/5

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

No annotations provided, and the description does not disclose side effects, permissions required, or what happens if a cel already exists at the target frame/layer. The term 'empty cel' is ambiguous.

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?

The description is very concise: one line plus a parameter list. No unnecessary sentences. However, it could include more helpful details without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return value, error conditions, or any prerequisites. The tool's behavior on conflict (e.g., existing cel) is undocumented.

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?

The description lists parameter names with minimal add-ons (e.g., 'X position in pixels'), but schema coverage is 0%, so the description must compensate. It fails to explain the coordinate system, units, or the meaning of 'empty' in relation to parameters.

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 clearly states the verb 'Create' and the resource 'empty cel on a layer/frame', which distinguishes it from sibling tools like set_cel_opacity or copy_cel. However, it lacks precision about what 'empty' means.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs. alternatives like copy_cel or set_cel_position. The description does not mention prerequisites or context for 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/ZeroTian/aseprite-mcp'

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