Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

invert_colors

Invert the active cel's RGB colors while leaving alpha transparency unchanged, with a single undoable edit.

Instructions

Invert the active cel's RGB (alpha untouched). One undo step.

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": "invert_colors"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: alpha is preserved and the change costs one undo step, which tells the agent how it interacts with the undo stack. The idempotentHint=false annotation is consistent with inversion being an involution rather than idempotent, so nothing contradicts. It still doesn't say what happens if no cel is active or what the response looks like.

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 action and effect, with no filler. Every clause carries information.

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?

For a simple single-effect tool with no output schema this covers the essential action and its undo/alpha semantics. It remains incomplete on the sole parameter and on the failure case of no active cel.

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

Parameters2/5

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

There is one optional parameter, 'file', with 0% schema description coverage, and the description never mentions it or what omitting it means. With coverage this low the description should compensate, and it does not.

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?

Names a specific verb and resource ('Invert the active cel's RGB') and scopes it to the active cel with the parenthetical 'alpha untouched', which separates it from a selection-wide inversion. It stops short of naming the sibling invert_selection, but the scope wording makes the distinction inferable.

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?

'Active cel' implies the precondition that a cel must be active, so usage context is implied rather than stated. There is no explicit when-to-use versus when-not, and no routing to invert_selection or undo alternatives.

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