Skip to main content
Glama
diivi
by diivi

create_cel

Add an empty cel to a specific layer and frame in an Aseprite file, positioning it 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 are available, so the description must disclose behaviors. It only states 'Create an empty cel' without explaining effects on existing cels, layer requirements, or side effects. Key behavioral traits are omitted.

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 concise with a single-line purpose and bullet-point parameter descriptions. It is front-loaded and avoids unnecessary text, though it could be slightly more structured.

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?

Given no annotations, no output schema, and many sibling tools, the description lacks context about what an 'empty cel' is, return values, or edge cases. It covers only the basics, missing important contextual completeness for an agent.

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%, so the description provides basic parameter explanations. For example, 'frame_index: Frame index starting at 1' and 'x: X position in pixels' add some meaning beyond the field names, but are still minimal.

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 'Create an empty cel on a layer/frame' using a specific verb and resource. This distinguishes it from sibling tools like copy_cel, clear_cel, and set_cel_position.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or conditions. The description only states what the tool does without context for selection.

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

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