Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

apply_preset_palette

Replace the current palette with a built-in preset such as gameboy, pico8, or cga to standardize pixel art colors for retro game assets.

Instructions

Replace the palette with a built-in preset: gameboy | pico8 | cga.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "apply_preset_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the load. It does disclose the key behavioral fact that the existing palette is replaced rather than appended, which is the main risk an agent needs to know. It says nothing about whether the prior palette is recoverable, what 'file' does, or whether the operation is global or per-document.

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?

A single front-loaded sentence with no filler; the action and the valid values arrive immediately. It is perhaps too terse given the undocumented parameter, but nothing is wasted.

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 two-parameter tool with no output schema, the description covers the required parameter's domain well. It falls short on the optional 'file' argument's meaning and on the consequences of replacement, which matter for a mutation of shared state.

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 coverage is 0%, so the description must compensate. It adds real value by enumerating the three legal values for the required 'name' parameter, which the schema does not constrain. However, the optional 'file' parameter is completely unexplained, leaving half the parameters undocumented.

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 ('Replace') plus resource ('the palette') plus the constrained set of accepted values (gameboy | pico8 | cga). That is enough to separate it from set_palette or load_palette in spirit, though no sibling is named 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 'built-in preset' implies this is for the three hard-coded palettes rather than arbitrary palette files or color edits, which is useful implied scoping. There is no explicit statement of when to prefer it over apply_bundled_palette, load_palette, or set_palette, and no exclusions.

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