Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by NosytLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apply_dither_gradient

Fill a rectangle with a two-color gradient using Bayer 4x4 ordered dithering, blending colors without introducing new intermediate hues.

Instructions

Fill a rectangle with a two-color gradient using Bayer 4x4 ordered dithering.

This is the classic pixel-art way to blend two colors without introducing new intermediate colors. The gradient runs from color_start (top/left) to color_end (bottom/right).

Args: filename: Aseprite file to modify layer_name: Layer to draw on frame_index: Frame index starting at 1 x: Left edge of the rectangle y: Top edge of the rectangle width: Rectangle width height: Rectangle height color_start: Hex color at the start of the gradient color_end: Hex color at the end of the gradient horizontal: Run the gradient left-to-right instead of top-to-bottom create_if_missing: Create the cel if it does not exist

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": {
      "filename": "<filename>",
      "layer_name": "<layer_name>",
      "frame_index": "<frame_index>",
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>",
      "color_start": "<color_start>",
      "color_end": "<color_end>"
    },
    "name": "apply_dither_gradient"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
widthYes
heightYes
filenameYes
color_endYes
horizontalNo
layer_nameYes
color_startYes
frame_indexYes
create_if_missingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It explains the gradient direction and parameter effects but does not disclose critical behaviors like overwriting existing pixels or whether the tool is destructive. The algorithm detail is useful, but safety aspects are lacking.

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?

The description is structured with a concise purpose statement followed by a well-formatted Args list. It front-loads key information without redundancy. A slight improvement could be removing the empty line between paragraphs.

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?

Given the tool's complexity (11 parameters, no output schema, no annotations), the description covers the core algorithm and parameter roles but omits edge cases like file existence checks, return value (e.g., success indicator), and what happens if the cel already exists.

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?

The schema has 0% description coverage, so the description compensates by listing all 11 parameters with meaningful one-liners (e.g., 'Hex color at the start of the gradient'). This adds significant value beyond the schema's property titles, though some format details (e.g., hex prefix) are implicit.

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?

The description clearly states it fills a rectangle with a two-color gradient using Bayer 4x4 ordered dithering, a specific technique for pixel art. This distinguishes it from sibling tools like apply_gradient_rect (smooth gradient) and apply_dither_pattern (pattern dither).

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 implies usage for pixel-art dithering ('classic pixel-art way') but does not provide explicit when-to-use or when-not-to-use guidance, nor does it name alternatives. The context is clear but not directive.

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