Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

apply_shading

Adds palette-constrained shading to a selected sprite region by brightening toward a light direction and darkening away, snapping pixels to the nearest palette color.

Instructions

Palette-constrained shading: brighten toward the light and darken away from it, snapping every pixel to the nearest palette color. intensity ~0..1. RGB sprite only; 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": "apply_shading"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
widthYes
heightYes
intensityNo
light_directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

With only a title annotation, the description carries the burden and does well: it discloses that every pixel is snapped to the palette (a lossy, constrained operation), that it produces one undo step, that it is RGB-only, and how to use it headlessly. It does not say what happens on out-of-palette or non-RGB input beyond exclusion.

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?

Three tight, front-loaded sentences: effect, key parameter range, then constraints. No filler; the RST-style backticks are the only mild noise.

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, 5-required mutation with no output schema and no annotations, the description covers the distinctive behavior and the file/intensity semantics but omits the bounding-region parameters and the light_direction format. An agent could invoke it, but would be guessing on those fields.

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

Parameters3/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: it explains intensity as ~0..1, conveys light_direction's meaning through 'toward the light', and flags file as the headless-mode input. It leaves x, y, width, height unexplained (presumably a region) and never gives accepted light_direction values, so compensation is partial.

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 specific operation with a clear effect: palette-constrained shading that brightens toward a light and darkens away from it, snapping to palette colors. This distinguishes it well from siblings like apply_dither or box_blur without naming them. It falls short of 5 only because it never explicitly contrasts itself with the nearest alternatives.

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 description gives constraints ('RGB sprite only', 'Headless: pass file') that tell the agent when the tool is applicable, but it never states when to prefer it over other shading/lighting tools such as add_rim_light or add_glow. Usage is implied by the effect description rather than explicitly guided.

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