Skip to main content
Glama
aimsise

color-engine

by aimsise

generate_ramp

Read-onlyIdempotent

Create a light-to-dark color ramp from any CSS color, including OKLCH values and WCAG contrast ratios per step. Optionally output as Tailwind JSON or CSS custom properties.

Instructions

Generate a tint-to-shade color ramp from a base CSS color. Returns an ordered list of swatches (light → dark) each with its in-gamut hex, display-rounded OKLCH components (l/c 5dp, h 2dp), WCAG contrast ratios (2dp) + tiers vs white and black, and an in-gamut flag. Optionally emits the ramp as design tokens via tokenFormat ("tailwind" JSON or a "css-variables" :root block).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesAny CSS color string, e.g. "#3b82f6", "oklch(0.6 0.35 30)" (max 256 chars)
stepsNoNumber of swatches (integer 2..512). Default 5.
deltaLNoTotal lightness span (> 0) centered on the base L — endpoints at base L ± deltaL/2 (overrides the fixed range).
tokenNameNoBase name for emitted tokens (letters/digits/hyphens, must start with a letter, 1-64 chars). Default "color".
tokenFormatNoOptional design-token format for the ramp ("tailwind" JSON object or a "css-variables" :root block); when present the output includes a `tokens` string.
lightnessMaxNoUpper lightness endpoint (OKLCH L, 0..1). Default 0.97.
lightnessMinNoLower lightness endpoint (OKLCH L, 0..1). Default 0.05.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokensNoDesign-token string for the ramp (pretty-printed Tailwind JSON or a :root CSS-variables block); present only when tokenFormat was supplied
swatchesYes
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds value by specifying the ordered light-to-dark output, included OKLCH components, WCAG contrast ratios, in-gamut flag, and optional token emission, giving a transparent view of the result structure.

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 two sentences, front-loaded with the main purpose, and includes detailed output specifications without unnecessary verbosity.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 7-parameter tool with an output schema, the description comprehensively covers the output format, ordering, optional design token formats, and computed metrics. No significant context is missing.

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 the baseline is 3. The description mentions tokenFormat and base color but does not add meaning beyond the schema's parameter descriptions. No gaps in parameter documentation exist.

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?

Description clearly states 'Generate a tint-to-shade color ramp from a base CSS color' with a specific verb and resource, differentiating it from sibling tools like parse_color and convert_color.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use case is clear—generating a color ramp from a base color—and the description implies this scope. However, it does not explicitly mention when not to use the tool or name alternatives, so it falls short of full usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aimsise/color-engine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server