Skip to main content
Glama

Generate palette

make_palette
Read-only

Generates a 50–950 OKLCH color scale and harmony colors from a base hex, with WCAG contrast against white and black for each step. Runs locally.

Instructions

From a base color, generates the 50–950 scale (Tailwind-style, computed in OKLCH) and harmony colors, with each step's WCAG contrast against white and black. Runs locally.

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

Input Schema

NameRequiredDescriptionDefault
baseYesBase color in hex, e.g. #3b82f6
nameNoColor name in the CSS variablesprimary
harmonyNocomplementary

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?

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing the actual output content (a 50–950 scale, harmony colors, and per-step WCAG contrast against white and black) and the OKLCH computation method. 'Runs locally' largely restates openWorldHint=false, but the output disclosure is genuinely additive.

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?

A single dense sentence with the resource, computation method, and outputs front-loaded; every clause carries information and nothing is padded. Parentheticals are used efficiently to scope 'Tailwind-style' and 'OKLCH'.

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

Completeness4/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 must describe the return, and it does so concretely (scale, harmony colors, contrast values). It stops short of indicating the response shape or that output is emitted as CSS variables, which slightly limits downstream use.

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?

With 67% schema description coverage and only three params, the schema already documents base, name, and the harmony enum. The description adds a little meaning for harmony ('harmony colors') but says nothing about the name parameter or how it maps into CSS variables, so it adds marginal value over the schema.

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?

The description opens with a clear verb and resource ('From a base color, generates the 50–950 scale ... and harmony colors') and specifies the OKLCH/Tailwind computation and WCAG contrast output, so an agent knows exactly what it produces. It does not, however, distinguish itself from the sibling check_contrast, which plausibly overlaps on contrast reporting.

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?

'From a base color' implies the prerequisite input, but there is no explicit when-to-use guidance, no when-not-to-use conditions, and no pointer to an alternative such as check_contrast for pure contrast queries. Usage must be inferred from the purpose statement.

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