Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

qa_sweep

Read-only

Audit the active sprite against project conventions and return pass/fail results for canvas size, grid multiple, color count, and symmetric padding checks.

Instructions

Audit the active sprite against project conventions and return per-check pass/fail. Any rule you pass is checked: exact canvas size (expected_width/expected_height), grid_multiple (canvas dims divisible by N), max_colors (distinct opaque colors ≤ N), and require_symmetric_padding (equal left/right + top/bottom margins). 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": "qa_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
max_colorsNo
grid_multipleNo
expected_widthNo
expected_heightNo
require_symmetric_paddingNo

Output Schema

NameRequiredDescriptionDefault
checksNo
failedNo
passedNo
measurementsNo

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?

Annotations already declare readOnlyHint=true, and 'Read-only' merely restates that. The description adds real behavioral context beyond the annotations: only rules explicitly passed are evaluated (unpassed checks are silently skipped), results are per-check pass/fail, and headless callers must supply ``file``. It does not cover error handling when no rules are supplied, which would be needed for 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.

Conciseness4/5

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

Purpose is front-loaded in the first clause, followed by the rule list and a terse operational note, with no filler sentences. The inline backtick-quoted parameter names make it scannable, though the rule enumeration runs slightly long as a single block.

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?

An output schema exists, so return format need not be explained, and all six parameters are given meaning in the description. Remaining ambiguity is minor: it never states what happens when no rules are passed, or how 'active sprite' is resolved when ``file`` is omitted.

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%, so the description must carry all parameter meaning, and it largely does: it defines expected_width/expected_height (exact canvas size), grid_multiple (dims divisible by N), max_colors (distinct opaque colors ≤ N), require_symmetric_padding (equal L/R and T/B margins), and file's headless role. The only gap is the default/null behavior — whether a nulled rule means the check is skipped entirely.

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 opens with a specific verb+resource ('Audit the active sprite') and enumerates the exact conventions it evaluates, so an agent knows precisely what the tool does. It does not differentiate from a plausibly overlapping sibling such as check_consistency, which keeps it from 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?

'Any rule you pass is checked' and 'Headless: pass ``file``' imply the usage model (pass rules to select checks; supply file when headless), which is useful but indirect. There is no explicit when-to-use vs when-not or comparison to alternatives, so guidance is only implied.

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