Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

expand_canvas

Grows or shrinks the canvas on any side without scaling existing pixel content, keeping pixels at their original positions in one undo step.

Instructions

Grow (or shrink, with negatives) the canvas per side WITHOUT scaling content — existing pixels keep their positions relative to the old origin. One undo step. Headless: pass file.

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": "expand_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
fileNo
leftNo
rightNo
bottomNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations carry only a title, so the description does the real work, and it delivers meaningful behavior: negative values shrink, existing pixels retain their origin-relative positions, and the whole operation is a single undo step. That undo granularity is exactly the kind of detail annotations would not have supplied. It stops short of saying what happens when a shrink exceeds the canvas bounds (whether pixels are clipped or an error is raised).

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?

Three short sentences, front-loaded with the core behavior and the no-scaling constraint, with no filler. The undo and headless notes are appended in priority order and each earns its place.

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 five-parameter mutation tool with no annotations, no output schema, and zero schema coverage, the description covers intent and the no-scale/undo semantics but omits units, defaults, edge behavior when shrinking past the canvas edge, and any return information. It is adequate to call the tool, 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%, so the description must carry parameter meaning, and it only partially does: it explains that the side parameters accept negatives to shrink, and that `file` is used in headless mode. It never states units (pixels), that top/left/right/bottom are independent per-side deltas with default 0, or what a zero value means, leaving half the parameters undocumented in both schema and description.

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 and resource (grow/shrink the canvas per side) and immediately clarifies the key semantic distinction: content is not scaled and pixels keep their positions relative to the old origin. This separates it from a resize-style tool. It does not explicitly name a sibling it is contrasted with, which keeps it just below a 5.

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?

Usage is implied rather than stated: 'WITHOUT scaling content' and 'negatives shrink' tell an agent what this tool is for, and 'Headless: pass file' gives a conditional invocation hint. There is no explicit when-not guidance or named alternative (e.g. a resize/crop tool) for the case where scaling is actually wanted.

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