Skip to main content
Glama

Generate Color Palette

generate_palette

Generate a complete accessible color system from one base color, including a 50–950 primary scale, harmony accents, tinted neutrals, semantic colors, and label colors.

Instructions

Generate a complete, accessible color system from one base color: a 50-950 primary scale, harmony accents, tinted neutrals, semantic colors (success, warning, danger, info) and the best label color on each primary step and each semantic color. Deterministic, no API key needed.

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

Input Schema

NameRequiredDescriptionDefault
baseYesBase brand color as hex, e.g. #e11d48
formatNojson
harmonyNoanalogous

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses determinism, that no API key is needed, and that accessibility is a built-in goal. It does not state failure modes for invalid hex input or whether output is purely computational, but the key behavioral traits are communicated.

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?

The description is a single tightly packed sentence followed by a short supporting clause, with the main purpose front-loaded and no filler. Every phrase contributes concrete information about the generated output.

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?

The output enumeration is rich and compensates for the missing output schema, but the tool has three parameters and no annotations, and the description says nothing about the format and harmony options. It is adequate but leaves meaningful gaps for an agent that must choose parameter values.

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

Parameters2/5

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

Schema description coverage is only 33%, and the description does not compensate. It mentions 'one base color' and 'harmony accents' but never explains the format parameter values (json/css/tailwind) or the harmony modes (monochromatic, analogous, complementary, etc.), leaving two of three parameters undocumented in prose.

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?

The description uses a specific verb and resource — 'Generate a complete, accessible color system from one base color' — and then enumerates exactly what is produced (50-950 scale, harmony accents, tinted neutrals, semantic colors, label colors). This clearly distinguishes it from sibling generators like generate_dark_theme or generate_chart_palette.

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 description implies usage by saying it builds a palette from a base color and notes it is deterministic with no API key needed, but it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives such as generate_dark_theme, generate_chart_palette, or check_contrast. The agent must infer the right context.

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