Skip to main content
Glama

generate_palette

Read-onlyIdempotent

Build a color palette from a base color using harmony types like analogous, complementary, or triadic. Generates readable swatches and filters disliked colors so agents can pick usable schemes.

Instructions

Generate a color palette using color theory harmonies (monochromatic, analogous, complementary, split-complementary, triadic, tetradic, square, compound, shades-and-tints). Defaults to perceptual HCT space, avoids universally disliked colors, and describes each swatch so agents can see what was generated.

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

Input Schema

NameRequiredDescriptionDefault
typeNoType of color harmonyanalogous
countNoNumber of colors to generate
spaceNoWheel space: 'hct' (perceptual default), 'oklch' (CSS perceptual), 'ryb' (painter's red-yellow-blue wheel), or 'hsl'hct
baseColorYesBase color for palette generation
allowDislikedNoAllow dark yellow-green 'bile zone' colors (default false)
includeDetailsNoInclude perceptual name, temperature, tone, and best text ink for each swatch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's job is easier. It still adds real value beyond them: the HCT default, the behavior of avoiding 'universally disliked' colors, the allowDisliked escape hatch, and the fact that each swatch is described so the agent can interpret output. It stops short of noting any filtering side effects on count outcomes when disliked colors are removed.

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?

A single front-loaded sentence with the core capability first and behavioral notes after. The nine-item harmony list duplicates the enum verbatim, which is mild redundancy, but the wording is otherwise tight and free of filler.

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?

With no output schema, the description carries the burden of explaining returns; it only says each swatch is 'described,' without stating the return shape (array of swatch objects, hex values, ordering). It does cover defaults, the disliked-color behavior, and the detail flag, which is adequate but not complete for a six-parameter generator.

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 description coverage is 100%, so all six parameters are already documented with enums and defaults. The description reinforces the harmony-type and space semantics but adds no format or syntax detail beyond the schema (e.g., accepted baseColor string forms like hex, name, or CSS color). Baseline 3 is appropriate.

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 ("Generate a color palette") and enumerates the harmonies it supports, so an agent knows exactly what it produces. It does not distinguish itself from siblings such as generate_tonal_palette, generate_categorical_palette, or generate_palette_with_locks, leaving the boundary implicit.

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 through the harmony-type list and the HCT default, which tell an agent this is for color-theory-based palettes. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives (locked palettes, tonal scales, categorical palettes) that an agent would need to choose correctly.

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