Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

paint_with_stamp

Stamps a PNG or cropped sprite region at multiple x,y points in one undoable Aseprite edit; optionally preview changed pixels and bounding box before committing.

Instructions

Stamp an image at each [x, y] in points (points are stamp centers). The stamp comes from source_path (a PNG) or source_rect ([x, y, width, height] cut from the composited sprite). One undo step for the whole scatter. Headless: pass file.

preview true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

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": {
      "points": "<points>"
    },
    "name": "paint_with_stamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
layerNo
pointsYes
previewNo
source_pathNo
source_rectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no readOnly/destructive annotations at all, the description carries the full burden, and it does disclose two useful traits: the whole scatter collapses into one undo step, and preview returns a before/after image plus changed-pixel count and bbox. It does not say what happens if neither source_path nor source_rect is supplied, how layer targeting affects the write, or whether the operation is reversible other than via undo.

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?

Four short, front-loaded sentences with no filler; the coordinate semantics and source options arrive before the undo and preview notes. Minor cost from backtick markup noise and the somewhat terse 'Headless: pass ``file``' construction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, and the description still explains the preview payload. For a six-parameter mutation tool with zero annotation coverage, the main residual gap is the undocumented layer parameter and the failure case when no source is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does for five of six parameters: points (stamp centers), source_path (PNG), source_rect ([x, y, width, height] cut from the composited sprite), file (headless mode), and preview (before/after + stats). The layer parameter is never explained, leaving the targeting semantics undocumented.

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 opens with a specific verb and resource ('Stamp an image at each [x, y] in points') and clarifies that points are stamp centers, which is concrete enough to picture the operation. It does not explicitly distinguish itself from the preset painters in the sibling list (paint_sky, paint_mountains, add_frame), so the agent must infer that this is the generic primitive.

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: the mention of 'one undo step for the whole scatter' and 'Headless: pass file' tells the agent how to invoke it in two modes, but there is no explicit when-to-use/when-not guidance or named alternative. Nothing steers the agent between this and the higher-level painting tools.

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