Zovo Palette Lab

Generate accessible palette

generate_accessible_palette

Read-onlyIdempotent

Use this when the user wants an accessible colour scale or palette built from one colour: "color palette generator from hex", "generate a 50-950 scale from #1E6FD9", "tailwind color palette generator", "accessible color palette for my website". Builds an 11-step 50-950 tonal scale in OKLCH with the base hue, where 50-400 pass AA with black text, 500 passes AA with both white and black text, 600 passes AA with white text and 700-950 pass AAA with white text, and each ratio is reported. Returns CSS custom properties and a Tailwind config as downloads. Does not pick colours by mood or brand meaning and does not extract palettes from images.

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_color": "<base_color>"
    },
    "name": "generate_accessible_palette"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Token name for CSS variables and the Tailwind colour key, e.g. brand (gives --brand-500). Default brand.
`base_color`	Yes	Brand or base colour to build the 50-950 scale from, e.g. #1E6FD9, rgb(30, 111, 217), oklch(55% 0.18 255) or teal.

Output Schema

Name	Required	Description	Default
`css`	Yes
`base`	Yes
`kind`	Yes
`name`	Yes
`pairs`	Yes
`rules`	Yes
`steps`	Yes
`request`	Yes
`tailwind`	Yes
`warnings`	Yes
`downloads`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare the safety profile (read-only, idempotent, non-destructive, closed-world); the description goes well beyond that with the exact contrast guarantees per step band (50-400 AA on black, 500 AA on both, 600 AA on white, 700-950 AAA on white) and the fact that each ratio is reported. It also discloses the algorithmic approach (OKLCH, base hue preserved) and that output arrives as downloadable CSS and Tailwind files.

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?

The trigger condition is front-loaded and every clause is substantive, with contrast bands as a compact list. The block of four quoted example utterances is slightly padded and could be trimmed to two without loss.

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?

Covers purpose, when to invoke, exclusions, guarantees, and output artifacts for a two-parameter tool, and an output schema exists so return-value structure is already handled. An agent has everything needed to decide and call correctly.

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 100% and both parameters already carry examples and defaults, so the schema does the heavy lifting. The description only restates that the palette is built from 'one colour'; it adds no format, constraint, or naming detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource: builds an 11-step 50-950 tonal scale in OKLCH from one base colour, and names the deliverables (CSS custom properties, Tailwind config). It is unmistakably different from the sibling contrast-checkers, since this one generates while those verify.

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?

Gives explicit trigger phrases ('color palette generator from hex', 'tailwind color palette generator') plus clear exclusions ('does not pick colours by mood', 'does not extract palettes from images'). It stops short of naming the sibling tools as the alternative for contrast verification, so routing to check_palette_contrast is left implicit.

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

All Zovo Palette Lab tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?