Skip to main content
Glama
Sign In
aseprite-mcp

aseprite-mcp

by shin2344234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

canvas_size

Grow or shrink an Aseprite sprite canvas without scaling pixels: add or cut margins, or set new width and height with an anchor.

Instructions

Grows or shrinks the canvas without scaling pixels: either margins (left/top/right/bottom, negative values cut) or a new width/height with an anchor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "canvas_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
leftNo
saveNoBatch mode: write changes back to the sprite file (default true)
rightNo
widthNo
anchorNo
bottomNo
heightNo
spriteNoFile path, open tab title, or sprite id. Defaults to the active sprite (live). Batch mode needs a file path.
backendNoauto (default): live Aseprite if connected, else headless batch
trimOutsideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive mutation, and the description adds useful behavioral detail that negative margin values cut pixels. It does not cover persistence (save default true), backend auto/live/batch behavior, or reversibility — though save and backend are documented in the schema, so the gap is moderate rather than severe. No contradiction with destructiveHint=false.

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?

A single dense sentence with zero filler, and the core behavior ('without scaling pixels') is front-loaded before the parameter modes. It could be marginally clearer about whether the two modes are mutually exclusive, but it earns its length.

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 an 11-parameter tool at 27% schema coverage with no output schema and no descriptive annotations, the description covers the core spatial parameters adequately but is silent on trimOutside, anchor value effects, and the live-vs-batch save implications. Adequate but with clear gaps for a tool this size.

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 only 27%, so the description carries real weight and it does explain left/top/right/bottom direction semantics and that negatives cut, plus the width/height+anchor mode. It leaves anchor selection meaning, trimOutside, and whether the two modes can be combined unexplained.

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?

States a specific verb (grows/shrinks) and resource (canvas) plus the key differentiator 'without scaling pixels', which implicitly separates it from resize_sprite. It doesn't name the sibling explicitly, but an agent can distinguish it.

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?

The 'either margins ... or width/height with an anchor' clause gives useful mode-selection context for the two ways to call it. However there is no explicit guidance on when to choose canvas_size over crop_sprite, resize_sprite, or trimOutside, so usage is only implied.

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