Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

resize_sprite

Scale an entire sprite to new pixel dimensions by specifying target width and height, enabling precise resizing of pixel art canvases for game assets.

Instructions

Scale the whole sprite to new pixel dimensions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "resize_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations contain only a title, so there is no readOnlyHint or destructiveHint to lean on and the description carries the full burden. It never says whether the resize happens in place, whether frames/layers are resampled, whether aspect ratio is preserved or stretched, or what resampling method is used — all material facts for a mutation tool.

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 front-loaded sentence with no filler; the core operation is stated immediately. It is efficient, though its brevity is also the source of the missing behavioral detail.

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?

For a mutation tool with zero meaningful annotations, no output schema, and 0% schema description coverage across three parameters, one sentence is not enough. An agent can guess the intent but cannot predict side effects, in-place behavior, or the role of the file argument.

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?

Schema description coverage is 0%, so the description must compensate for all three parameters. 'New pixel dimensions' does clarify the units for width and height, but the optional 'file' parameter is completely unexplained, and there is no note on required-vs-optional behavior or unit constraints.

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?

Names a specific verb (scale) and resource (sprite) and scopes it with 'whole sprite', which distinguishes it from crop_sprite and autocrop_sprite in the sibling list. The only ambiguity is how it relates to batch_resize, which the description never addresses.

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?

The description says nothing about when to pick this tool over batch_resize for multiple sprites, or over crop_sprite when only part of the image should change dimensions. No prerequisites, no mention of whether a sprite must be open or pinned first.

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