Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

select_palette

Switches the active palette by name, choosing a global or project palette. In indexed mode it recolors the whole image slot by slot to match that palette.

Instructions

Select a palette by name (global or project palette). In indexed mode the whole image recolors to it, slot by slot.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a real side effect: in indexed mode the entire image recolors slot by slot. It stops short of stating failure behavior for unknown names, whether the change is undoable, or which palette wins when a global and project palette share a name.

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 primary action first and the consequence second; nothing is padded or redundant.

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 one-parameter mutation tool with no annotations and no output schema, the description covers the main effect but leaves the agent guessing about invalid-name behavior and confirmation/return state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'name' parameter, so the description must compensate. It adds that the name may refer to a global or project palette, which is genuine resolution semantics, but says nothing about case sensitivity, format, or how ambiguity between the two namespaces is resolved.

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 ('select') plus resource ('palette') and a scope note that the name may resolve to a global or project palette. It is clearly distinct from create_palette/get_palette, though it does not name those siblings 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?

Usage is implied rather than stated: use it to activate an existing palette. There is no guidance on what to do when the name does not exist (create_palette?) or how selection relates to other state-changing tools.

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