Skip to main content
Glama
Sign In
pixel-art-mcp

pixel-art-mcp

by comficker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List built-in palettes

list_palettes

Lists built-in pixel art palettes and their colors, helping you choose a palette for recoloring sprites or converting images to pixel art.

Instructions

List the built-in pixel art palettes and their colours.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It makes clear the result set is fixed ('built-in') and includes colour values, which is useful. It does not state whether the listing is paginated, how many palettes exist, or the shape of each entry.

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?

One short, front-loaded sentence with no filler. The resource and its contents are stated immediately.

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?

For a zero-parameter read tool with no output schema, the description covers what the tool returns (palettes plus colour data). It stops short of describing the entry format or overall count, which an agent composing a follow-up call might want.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The stated return content ('palettes and their colours') is a useful hint about what each entry contains.

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?

Names a specific verb (list) and resource (built-in pixel art palettes) with the payload ('their colours'). It implicitly separates itself from extract_palette by scoping to 'built-in', but never names a sibling 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 word 'built-in' hints that this is the reference/enumeration tool rather than a palette-derivation tool, but there is no explicit when-to-use or when-not, and it doesn't route the agent to extract_palette or remap_palette.

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