Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

desaturate

Convert the active cel to grayscale using Rec. 601 luma while preserving alpha, with a single undo step; pass a file for headless use.

Instructions

Convert the active cel to grayscale (Rec. 601 luma), keeping alpha. 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": "desaturate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations supply only a title, so the description carries the full behavioral load and does add real context: alpha channel is preserved, the operation costs exactly one undo step, and headless calls require a file path. Missing are failure modes (e.g. no active cel) and any return-value description, which keeps this short of a 5.

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?

Two short sentences, front-loaded with the core operation and followed by the two behavioral caveats (undo cost, headless file). No repetition of the title or schema and no wasted words.

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 low-complexity, single-optional-parameter mutation tool, the description covers purpose, alpha behavior, undo semantics, and the headless parameter. It is nearly complete; only error/return behavior is absent, which is a minor gap given no output schema 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?

Schema description coverage is 0% for the sole `file` parameter, so the schema alone leaves it meaningless. The description compensates by explaining that `file` is the headless-mode input, adding genuine semantics the schema lacks.

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 ("Convert the active cel to grayscale") and even names the exact luma formula (Rec. 601), which distinguishes it from siblings like adjust_hsl and adjust_brightness_contrast. An agent can identify the operation without opening the schema.

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 headless note ("Headless: pass ``file``") gives context for one calling mode, but there is no explicit when-to-use guidance or named alternative (e.g. when to prefer adjust_hsl for tinting vs desaturation). Usage is only implied by the operation name.

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