Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by ZeroTian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_palette

Replace the active sprite palette by providing a list of hex color codes.

Instructions

Set the active sprite palette using a list of hex colors.

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": {
      "filename": "<filename>",
      "colors": "<colors>"
    },
    "name": "set_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
colorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, and the description gives no behavioral details beyond the fact that it sets the palette. It does not disclose side effects (e.g., replacing entire palette), validation, or error conditions.

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

Conciseness3/5

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

The description is a single sentence, very concise, but it sacrifices necessary detail. It could be improved by adding parameter explanations without significant length increase.

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

Completeness2/5

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

For a tool with two required parameters and no output schema or annotations, the description is too minimal. It fails to provide context for the 'filename' parameter, any constraints, or expected outcomes.

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?

The description adds meaning to the 'colors' parameter (list of hex colors) but does not explain the 'filename' parameter at all. With 0% schema description coverage and only one of two parameters clarified, the description is insufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (set), the target (active sprite palette), and the method (using a list of hex colors). It distinguishes from siblings like 'get_palette' and 'apply_palette_preset' by specifying the input format.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or context provided. The agent must infer usage from the bare description.

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