lentera-aseprite-mcp

load_palette_lentera

Loads the official Lentera Pudar 8-color palette, supplying the exact colors (warm yellow, cold blue, etc.) to ensure consistent pixel art across the project.

Instructions

Load the official Lentera Pudar 8-color palette (#F4B860 warm yellow, #4A6FA5 cold blue, etc.). Use this always for Lentera Pudar art.

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": "load_palette_lentera"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 14, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description names the palette and colors, but does not disclose side effects such as whether it replaces the current palette entirely or preserves other slots. Since no annotations exist, more clarity on how it interacts with the current palette would be beneficial. However, 'load' implies setting the palette, so basic behavior is conveyed.

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?

Two short sentences, with the essential information first. No fluff, and the color list adds value without clutter.

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

Completeness4/5

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

This simple tool is adequately explained for its low complexity. It lacks an explicit statement about palette size resetting, but includes the colors and usage context, covering the core behavior needed by an agent.

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?

There are zero parameters, so the description doesn't need to explain any. The palette definition is fully specified in the description, making the tool self-contained.

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 identifies the action (load) and the specific resource (official Lentera Pudar 8-color palette) with actual color values. It distinguishes itself from sibling tools like load_palette_from_file by targeting a built-in palette.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides a clear directive to use this tool for Lentera Pudar art. It does not explicitly mention alternatives or exclusions, but the context is sufficient for selection.

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