Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_gradient

Fills a rectangle with a linear gradient between two colors, horizontally, vertically, or diagonally. Uses ordered Bayer dithering for palette-friendly results in pixel art.

Instructions

Fill a rectangle with a linear gradient from color1 to color2. direction is horizontal | vertical | diagonal. dither true uses an ordered Bayer dither between the two colors instead of blending RGB — the palette-friendly way. With dither, bands above 1 steps through that many solid colors and dithers only the seams, which reads far cleaner than one dither across a tall area. 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

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>",
      "color1": "<color1>",
      "color2": "<color2>"
    },
    "name": "draw_gradient"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
bandsNo
widthYes
color1Yes
color2Yes
ditherNo
heightYes
previewNo
directionNovertical

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?

Annotations carry only a title, so the description must carry the full behavioral burden; it does disclose the key facts — 'One undo step', the headless file requirement, and that preview adds return data beyond the paletted pixels. It does not state whether existing pixels are overwritten, what happens on out-of-bounds rects, or permission requirements, leaving gaps for a mutating canvas operation.

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 action, then a compact sequence of conditional rules; every sentence adds information. ReST-style backticks and the longer parenthetical on bands add minor noise but no wasted sentences.

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?

Given an output schema exists, the description need not detail return values, yet it still flags what preview returns (before/after image, changed-pixel count, bbox). Combined with undo and headless notes, it is nearly complete; the missing geometry parameter meanings and overwrite semantics are the remaining gaps.

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 coverage is 0% across 11 params, so the description is the only source of meaning; it covers direction's allowed values, dither's algorithm, bands' interaction with dither, file's headless role, and preview's effect — roughly 7 of 11 params. x, y, width, height are never described in text or schema, leaving the rectangle geometry 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?

States a specific verb and resource ('Fill a rectangle with a linear gradient from color1 to color2'), which is inherently distinguishable from draw_rectangle and other draw_* siblings. It does not explicitly contrast itself with apply_dither or the solid-fill siblings, so sibling differentiation is only implicit.

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?

Gives conditional guidance: use dither for palette-friendly output, use bands>1 on tall areas to avoid muddy seams, and pass file in headless mode. It never names an alternative (e.g. apply_dither) or states when not to use this tool, so the alternative-routing piece is missing.

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