Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_palette

Read-only

Retrieves an Aseprite sprite's palette as #rrggbbaa hex strings, enabling exact color inspection and reuse in pixel-art or asset export workflows.

Instructions

Return the active sprite's palette as #rrggbbaa hex strings.

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_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds useful behavioral detail — the exact return encoding of #rrggbbaa — but says nothing about ordering, size, empty-palette behavior, or the effect of the file parameter.

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?

One sentence, zero filler, with the return format front-loaded. Nothing could be removed without losing 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?

With no output schema, the description correctly specifies the return format, which is the most important missing piece. However, the sole input parameter is left unexplained and there is no mention of palette ordering or behavior when no sprite is active.

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?

Schema description coverage is 0% for the single optional 'file' parameter, so the description must compensate and does not. Worse, calling the target "the active sprite" suggests the file argument may be irrelevant, without clarifying what 'file' selects or what its default (null) means.

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 the active sprite's palette") plus the exact encoding (#rrggbbaa hex strings), so an agent knows precisely what comes back. It does not explicitly distinguish itself from palette-related siblings such as get_color_stats or palette_from_sprite, so it stops short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no reference to alternatives. The word "active" implies a current-sprite context but the description never says what to do when another sprite or file is of interest, leaving the agent to infer.

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