Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

save_palette

Export a sprite's palette to .gpl, .pal, or .png files; the file extension determines the saved format.

Instructions

Write the sprite's palette to a file (.gpl, .pal, .png — by extension).

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": {
      "path": "<path>"
    },
    "name": "save_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

Annotations supply only openWorldHint=true and a title; there are no readOnly/destructive hints, so the write-to-disk behavior rests on the description. It usefully discloses that the output format is chosen from the file extension (.gpl/.pal/.png), but says nothing about overwriting existing files, error behavior, or what gets returned.

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 tight sentence with the payload at the front and the format rule woven in; no filler. It is arguably slightly too terse given the unexplained second parameter.

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 simple save tool with no output schema this covers the essentials of what is written and in what format. Missing pieces are the meaning of the 'file' parameter, overwrite semantics, and any hint about where files land.

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 coverage is 0%, so the description must carry parameter meaning. It clarifies that 'path' drives format selection via extension, but the optional 'file' parameter (default null) is completely unexplained, leaving an ambiguous two-way relationship between 'file' and 'path'.

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?

Specific verb+resource: 'Write the sprite's palette to a file', plus supported formats. It is distinguishable from save_sprite/save_all_sprites by scoping to the palette, though it never explicitly contrasts itself with them or with set_palette/load_palette.

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 versus save_sprite, save_all_sprites, or apply_preset_palette, and no callouts such as prerequisites or overwrite behavior. The only usage-relevant fact is format-by-extension, which is more mechanism than guidance.

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