Skip to main content
Glama
ZeroTian

Aseprite MCP Tools

by ZeroTian

resize_canvas

Scale the canvas and its content to new dimensions by specifying width and height in pixels.

Instructions

Scale the canvas and all its content to new dimensions.

Args: filename: Aseprite file to modify width: New canvas width in pixels height: New canvas height in pixels

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
widthYes
heightYes
Behavior2/5

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

The description states that content is scaled to new dimensions but does not disclose whether aspect ratio is preserved, what happens if dimensions are smaller/larger, or any restrictions like minimum size. No annotations are present to supplement this.

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 efficient: a single sentence summarizing the action followed by a brief parameter list. No extraneous text, but the structure could be slightly improved (e.g., bullet points).

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?

Given the tool's simplicity and lack of output schema, the description covers basic purpose and parameters. However, it omits important behavior (e.g., scaling mode, background handling) that an agent would need for correct invocation.

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?

With 0% schema description coverage, the description provides basic explanations for each parameter (e.g., 'New canvas width in pixels'). This adds minimal meaning beyond the schema, but does not include constraints or format details.

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 uses a specific verb 'Scale' and identifies the resource 'canvas and all its content' with the action of setting new dimensions. It clearly distinguishes from sibling tools like 'crop_canvas' which removes content, and 'create_canvas' which creates a new canvas.

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 such as 'crop_canvas' or 'resize via content scaling'. The description lacks context on prerequisites or exclusions.

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