Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

adjust_hsl

Shift the active cel's colors in HSL by adjusting hue degrees, saturation multiplier, and lightness delta to create tint variants in one undo step.

Instructions

Shift the active cel's colors in HSL: hue_shift degrees (-360..360), saturation a multiplier (1.0 = unchanged), lightness a delta (-1..1). Useful for tint variants. One undo step. Headless: pass file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adjust_hsl"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
hue_shiftNo
lightnessNo
saturationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the behavioral load and does add real context: it is a mutation that consumes exactly 'one undo step', it targets the 'active cel' rather than an arbitrary one, and it requires a file argument in headless mode. It does not cover failure modes (e.g. no active cel) or the return value, but the undo-scope and headless notes are substantive.

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?

Front-loaded with the core action and color model, then parameter semantics inline with their ranges, then two short behavioral notes. No sentence is filler; even 'Useful for tint variants' serves as the use-case cue.

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 zero-required-parameter mutation with no output schema and minimal annotations, the description covers the operation, all parameter meanings, undo cost, and headless invocation. What remains unstated is behavior when no cel is active and what the tool returns, both minor for this complexity level.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for all four parameters: hue_shift in degrees bounded -360..360, saturation as a multiplier with 1.0 = unchanged, lightness as a signed delta -1..1, and file for headless use. The multiplier-vs-delta distinction is exactly the kind of meaning bare parameter names cannot convey.

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 ('Shift') and resource ('the active cel's colors') and pins the color space to HSL, which separates it from the sibling adjust_brightness_contrast. It does not explicitly name a sibling or say when that alternative is preferred, so it stops just short of a 5.

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?

'Useful for tint variants' gives an intended use case, and 'Headless: pass file' tells the agent when the file parameter matters. There is no explicit when-not guidance and no named alternative among siblings like adjust_brightness_contrast, so usage is implied rather than prescribed.

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