Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

crop_sprite

Destructive

Crop a sprite to a specified rectangle using x, y, width, and height coordinates, trimming the canvas to just the pixel art region you need.

Instructions

Crop the sprite to the given rectangle.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "crop_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotation already declares destructiveHint=true, but the description adds no behavioral context beyond that. It does not say whether the crop modifies the active sprite in place, whether the original content is lost, or how the optional file parameter affects behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. However, it is too terse for a five-parameter destructive operation, making the brevity a liability rather than a strength.

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 destructive mutation tool with five parameters, no output schema, and no parameter descriptions, the definition is significantly under-specified. It leaves an agent without enough information to invoke the tool confidently.

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 carry parameter meaning. 'Given rectangle' loosely implies x, y, width, and height, but it does not explain coordinate origin, units, clipping behavior, or what the optional file parameter does.

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?

The description states a specific verb and resource: crop the sprite. The phrase 'to the given rectangle' clarifies the operation, though it does not explicitly distinguish this from siblings like autocrop_sprite or resize_sprite.

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?

There is no guidance on when to use crop_sprite versus related tools such as autocrop_sprite, resize_sprite, or flip_sprite. No prerequisites or usage context are provided.

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