Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

generate_color_ramp

Generates a dark-to-light shading ramp from a base color and appends it in order to the active palette, returning hex values ready for palette ramp walking.

Instructions

Generate a dark->light shading ramp from base_color and APPEND it to the palette in order — ready for palette_ramp_walk. count colors; hue_shift pushes shadows toward blue and highlights toward yellow. Returns the ramp as hex. 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": {
      "base_color": "<base_color>"
    },
    "name": "generate_color_ramp"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
countNo
hue_shiftNo
base_colorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

With only a title annotation, the description does real work: it discloses that the tool mutates the palette by appending, that it constitutes exactly 'One undo step', that output is hex, and that headless runs need file. It does not say what happens to pre-existing palette entries beyond appended ordering or whether the append can be scoped/skipped, so it is good but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very tight: the primary action and side effect are front-loaded, then parameters, return format, undo cost, and headless note each get a short clause. No filler 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?

For a 4-parameter mutation tool with no output schema and no annotations, the definition covers action, side effect, return format, undo cost, and headless requirement. Gaps are small (ordering semantics of the append, base_color format), so it is close to complete.

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?

Schema coverage is 0%, so the description must carry the load and largely does: count is the number of colors, hue_shift is explained concretely (shadows toward blue, highlights toward yellow), file is tied to headless operation, and base_color is identified as the ramp source. Minor ambiguity remains about count bounds and accepted base_color format.

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?

States a specific verb and resource (generate a dark->light shading ramp from base_color) plus the concrete side effect (APPEND it to the palette in order). It also names the downstream sibling palette_ramp_walk, so an agent can place it in a workflow without opening another 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?

Gives clear context: use it when you want a ramp appended in order and then walked with palette_ramp_walk, and pass file when running headless. It stops short of explicit when-not-to-use guidance or naming alternatives (e.g., add_palette_color), which keeps it at 4 rather than 5.

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