Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

palette_ramp_walk

Shades pixel art by walking a hand-ordered palette ramp ±N indices toward lighter or darker colors, so luminance jumps and broken shading order are avoided. One undo step.

Instructions

Shade by WALKING the arranged palette ±N indices toward lighter/darker (per light direction), instead of snapping to the luminance-nearest color — so hand-ordered shading ramps are respected. steps = max indices to walk at the fully-lit/shadowed edges. RGB sprite with an ordered ramp palette; one undo step. Headless: pass file.

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>",
      "light_direction": "<light_direction>"
    },
    "name": "palette_ramp_walk"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
stepsNo
widthYes
heightYes
light_directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations carry no readOnly/destructive hints, so the description bears the burden and does well: it discloses that the operation is a single undoable mutation ('one undo step'), states the required sprite/palette precondition, and flags headless usage via 'file'. It does not say what happens when the palette is unordered or how failures surface.

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 mechanism and the differentiator, then the `steps` semantics, then preconditions and headless note. Dense but each clause earns its place; the backticked parameter callouts keep it scannable.

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 7-parameter mutating tool with no output schema and only a title annotation, the description covers concept, undo behavior, and a headless path, but leaves the region parameters and light_direction's accepted values undocumented, which an agent needs to call it correctly.

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% for 7 parameters, so the description must compensate. It meaningfully defines only `steps` (max indices walked at fully-lit/shadowed edges) and `file` (headless); x, y, width, height (apparently a region) and especially `light_direction` (no enum, no format) are left ambiguous.

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 precise verb and mechanism: shading by walking the arranged palette ±N indices toward lighter/darker. It also contrasts itself against luminance-nearest snapping, which effectively separates it from quantize/palette-apply siblings, though no sibling is named outright.

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?

The precondition 'RGB sprite with an ordered ramp palette' tells the agent when this tool is applicable, and the contrast with luminance-nearest snapping implies when it should be preferred. However, there is no explicit when-to-use/when-not language and no named alternative for non-ordered palettes.

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