Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_outline

Adds a 1px color outline around opaque pixels on a layer to improve sprite readability against busy backgrounds; supports selective color-following, diagonal edges, and all frames.

Instructions

Add a 1px outline around the opaque pixels of a layer, in color — readability against busy backgrounds. selective true ignores color and darkens each neighbouring pixel's own color instead, for a softer outline that follows the art (RGB sprites). diagonal true also outlines diagonally (8-connected). layer picks the layer, and all_frames outlines every cel on it rather than the active one. One undo step. Headless: pass file.

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

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

Input Schema

NameRequiredDescriptionDefault
fileNo
colorNo#000000
layerNo
previewNo
diagonalNo
selectiveNo
all_framesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/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: it discloses the mutation cost ('One undo step'), the headless precondition ('pass file'), the contrast between 'all_frames' and the active cel, and that 'preview' returns a before/after canvas image plus changed-pixel count and bbox. That is substantial behavioral context; it only lacks failure modes (e.g. what happens on a layer with no opaque pixels) to reach the top.

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?

Front-loaded with the core effect, then parameter behaviors, then mutation/headless notes. Every clause carries information, though the ordering is slightly untidy — the 'preview' output note trails after the undo/headless sentence rather than sitting with the other output-related detail.

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

Completeness5/5

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

For a 7-parameter editing tool with no meaningful annotations, the definition covers what it does, how each argument changes behavior, the undo cost, and the headless requirement. An output schema already exists, yet the description still usefully characterizes the preview payload, leaving nothing an agent needs missing.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description compensates for every one of the 7 parameters: color default behavior, the key interaction that 'selective' ignores color and darkens neighbouring pixels, 'diagonal' as 8-connected, 'layer' selector, 'all_frames' vs active cel, 'preview' return content, and 'file' for headless use. This is exactly what a 0%-coverage schema needs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource+scope: 'Add a 1px outline around the opaque pixels of a layer', and immediately names its purpose 'readability against busy backgrounds'. The effect is described precisely enough (1px, opaque pixels only, per-layer) that an agent can distinguish it from neighbouring visual-effect siblings such as glow or rim light without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear use context ('readability against busy backgrounds') and states the condition that selects the main variant: 'selective true ... for a softer outline that follows the art (RGB sprites)'. It never states when not to use it or names an alternative tool, so it stops short of full when/when-not guidance.

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