Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_color_stats

Read-only

Generate a composited sprite color histogram to count distinct opaque colors, total opaque pixels, and top-used colors for palette-drift checks during art QA.

Instructions

Return a color histogram of the composited sprite: distinct opaque color count, total opaque pixels, and the top most-used colors with counts — a palette-drift check for the art-QA loop. Read-only. 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": "get_color_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint already declared, 'Read-only.' earns no credit, but the description does add real behavioral context: the histogram is computed over the *composited* sprite (not per-layer source pixels), and in headless mode the 'file' parameter must be supplied. It also discloses the shape of the result, which matters because no output schema exists.

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

Conciseness4/5

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

One dense sentence plus two short fragments, front-loaded with the resource and the returned metrics before the use case. Minor waste: 'Read-only.' merely restates the annotation instead of adding new information.

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

Completeness5/5

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

No output schema exists, yet the description enumerates every returned value the agent needs to interpret the result, and it covers both parameters' roles plus the headless constraint. For a two-parameter read-only stats tool, nothing essential for a correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the burden for both parameters. It clarifies that 'top' bounds how many most-used colors are returned and that 'file' is the headless-mode input, but it never explains what 'file' points to (a sprite path?) or what the null default implies (use the open document), leaving real ambiguity.

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 and resource ('Return a color histogram of the composited sprite') and enumerates the exact outputs: distinct opaque color count, total opaque pixels, and top colors with counts. That is far more specific than a sibling like get_palette, though it never names an alternative to draw the boundary explicitly.

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 phrase 'a palette-drift check for the art-QA loop' implies the scenario where this tool is the right choice, and 'Headless: pass file' hints at the non-interactive mode. However, there is no explicit when-not-to-use guidance and no named alternative (e.g. get_palette for palette definitions), so the routing decision is left partly to inference.

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