Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

get_palette

Retrieves the selected palette's slot numbers and colors, all palette names, and the current color mode for use with '@n' color references in draw and fill operations.

Instructions

Show the palette selected in Pixelorama (slot number and color of every swatch, slot 0 first), the names of all palettes, and the color mode. In draw_pixels and fill_rect a color '@n' means slot n of this palette.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so by framing the operation as a read ("Show") with no side effects implied, and by pinning down exactly what state is reported. It does not discuss permissions or behavior when no palette exists, but for a zero-parameter read tool the behavioral picture is essentially complete.

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 compact sentences with zero filler. The return content is front-loaded and the '@n' cross-reference follows as supporting context rather than padding.

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

Completeness5/5

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

No output schema exists, so the description must describe the return value itself, and it does: swatch slot numbers and colors with slot 0 first, all palette names, and the active color mode. Nothing needed to call or interpret this tool correctly is missing.

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 no parameters, so there is nothing to disambiguate; the baseline for a 0-param schema applies. The description instead spends its words on the interpretation of the returned slot indices, which is the closest analogue to parameter semantics here.

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?

States a specific verb and resource ("Show the palette selected in Pixelorama") and enumerates the exact payload: slot number, color of every swatch, palette names, and color mode. This is immediately distinguishable from siblings like get_image, get_project, and select_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 ties the tool to concrete downstream use by explaining that '@n' in draw_pixels and fill_rect refers to slot n of this palette, which tells an agent why and when to call it. It stops short of explicit routing guidance such as when to prefer select_palette or create_palette instead, so it is clear context rather than a full when/when-not statement.

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