Aseprite MCP

Overview Schema Source Related Servers Discussions Admin

adjust_hue_saturation

Shift hue and scale saturation/lightness of Aseprite sprites to adjust colors. Use for pixel art color correction or variation.

Instructions

Shift hue (degrees) and scale saturation/lightness (percent, -100..100).

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>"
    },
    "name": "adjust_hue_saturation"
  }
}

Input Schema

Name	Required	Description
`hue`	No	Default: 0.
`frame`	No	Default: 1.
`layer`	No
`filename`	Yes
`lightness`	No	Default: 0.
`saturation`	No	Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.10.0Oct 4, 2026
- removedInput schema / properties / filename / title
```
Removed value: -"Filename"
```
- addedInput schema / properties / frame / description
```
Added value: +"Default: 1."
```
- removedInput schema / properties / frame / title
```
Removed value: -"Frame"
```
- addedInput schema / properties / hue / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / hue / title
```
Removed value: -"Hue"
```
- removedInput schema / properties / layer / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / layer / default
```
Removed value: -null
```
- removedInput schema / properties / layer / title
```
Removed value: -"Layer"
```
- addedInput schema / properties / layer / type
```
Added value: +"string"
```
- addedInput schema / properties / lightness / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / lightness / title
```
Removed value: -"Lightness"
```
- addedInput schema / properties / saturation / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / saturation / title
```
Removed value: -"Saturation"
```
- removedInput schema / title
```
Removed value: -"adjust_hue_saturationArguments"
```
First observedv0.7.0Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations declare readOnlyHint=false, so the agent knows this is a mutating operation. However, the description does not disclose what exactly gets modified (e.g., a specific layer or frame in a file), whether changes are reversible, or any permission requirements. It adds only the units and range for the adjustment values, not the behavioral context of a mutation.

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?

The description is a single, front-loaded sentence that is appropriately sized and contains no filler. Every part, the operations and the units, earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 6 parameters (including required filename, plus layer and frame targeting) and no output schema, the description is too thin. It explains the adjustment values but not what object is being modified or how the target is selected, leaving significant gaps for correct invocation.

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 description coverage is 67%, and for the core adjustment parameters the schema only says 'Default: 0.' The description adds crucial meaning by specifying that hue is in degrees and saturation/lightness are percentages in the -100..100 range. It does not clarify the roles of filename, layer, or frame.

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?

The description states a specific operation: shifting hue and scaling saturation/lightness. It is clear about what adjustments are performed but does not differentiate this tool from close siblings like adjust_brightness_contrast or desaturate, nor does it mention the target resource (file, layer, frame).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives such as desaturate or adjust_brightness_contrast. It gives no prerequisites or context for selection, leaving the agent to infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server