Skip to main content
Glama
ext-sakamoro

Aseprite MCP Tools

by ext-sakamoro

apply_preset_palette

Apply a predefined color palette to an Aseprite file. Choose from classic palettes like gameboy, nes, or pico-8 to quickly modify pixel art colors.

Instructions

Apply a predefined palette to an Aseprite file.

Args: filename: Name of the Aseprite file to modify preset: Preset palette name. Options: gameboy, gameboy-pocket, nes, pico-8, cga, monochrome, sepia

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
presetYes

Implementation Reference

  • The handler function 'apply_preset_palette' which validates the preset name and calls 'create_palette' to update the Aseprite file.
    async def apply_preset_palette(
        filename: str,
        preset: str
    ) -> str:
        """Apply a predefined palette to an Aseprite file.
    
        Args:
            filename: Name of the Aseprite file to modify
            preset: Preset palette name. Options: gameboy, gameboy-pocket, nes, pico-8, cga, monochrome, sepia
        """
        try:
            preset_lower = preset.lower()
            if preset_lower not in PRESET_PALETTES:
                available = ", ".join(sorted(PRESET_PALETTES.keys()))
                raise ValidationError("preset", preset, f"Unknown preset. Available: {available}")
            
            colors = PRESET_PALETTES[preset_lower]
            return await create_palette(filename, colors, palette_name=preset)
            
        except Exception as e:
            return f"Failed to apply preset palette: {e}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this modifies a file ('to modify'), implying mutation, but doesn't disclose whether this overwrites existing palettes, requires file permissions, or has side effects. The description adds minimal behavioral context beyond the basic action.

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?

Perfectly front-loaded with the core purpose in the first sentence, followed by structured parameter details. Every sentence earns its place with no wasted words, and the parameter list is efficiently formatted.

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 2-parameter mutation tool with no annotations and no output schema, the description is minimally complete. It covers what the tool does and parameter options, but lacks details on behavioral consequences, error conditions, or return values. Given the complexity, it should provide more operational context.

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 compensate. It provides clear semantics for both parameters: 'filename' specifies the target file, and 'preset' lists all valid options (gameboy, gameboy-pocket, etc.). This adds essential meaning beyond the bare schema.

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 specific action ('Apply a predefined palette') and target resource ('to an Aseprite file'). It distinguishes from siblings like 'create_palette' (makes new) and 'extract_palette_from_image' (extracts from image) by focusing on applying existing presets.

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 description implies usage when you want to apply a preset palette to a file, but doesn't explicitly state when to use this vs alternatives like 'batch_apply_palette' (for multiple files) or 'remap_colors' (for custom color mapping). No prerequisites or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ext-sakamoro/AsepriteMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server