Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

create_palette

Creates and selects a project palette from an ordered color list, keeping slot 0 first so day and night palettes can reuse the same slot order.

Instructions

Create a project palette from a list of colors (slot 0 first) and select it. Use the same slot order for a day and a night palette.

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>",
      "colors": "<colors>"
    },
    "name": "create_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
widthNoSwatches per row in the palette panel, default 8
colorsYesColors as #rrggbb, slot 0 first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 an important side effect: the new palette is also selected, changing current state. It does not say what happens if a palette with the same name already exists, whether creation is reversible, or what the call returns (no output schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and side effect; nothing is padding. The second sentence is context-specific but short and does add a usable convention.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the essential create-and-select behavior. It leaves notable gaps: the meaning of 'name', duplicate-name handling, and the return value.

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 67%: colors and width are already documented in the schema, including 'slot 0 first' and the default of 8. The description restates the slot ordering and adds a cross-palette consistency convention, but the required 'name' parameter is unexplained in both schema and description.

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?

States a specific verb and resource ('Create a project palette') and names the input basis ('from a list of colors'), plus the side effect 'select it'. It implicitly distinguishes itself from the sibling select_palette by pairing creation with selection, though it does not name any 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 second sentence gives a workflow convention (reuse the same slot order when building a day and a night palette), which is real usage guidance. However, there is no explicit statement of when to use this versus select_palette/get_palette, nor any prerequisite or exclusion.

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