Skip to main content
Glama

design_ui_palette

Read-onlyIdempotent

Builds a contrast-verified Light and Dark UI color system from one brand color using the 60-30-10 rule, producing surface, text, CTA, and status colors that meet WCAG AA/AAA.

Instructions

Design a complete, contrast-verified Light + Dark UI color system from a single brand color following the 60-30-10 rule (60% surfaces/neutrals/text hierarchy, 30% secondary & subtle containers, 10% primary CTA & interactive states + harmonized status colors). Prevents dark-mode neon halation and guarantees WCAG AA/AAA text pairs.

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": {
      "brand": "<brand>"
    },
    "name": "design_ui_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand seed color (hex, CSS name, rgb, hsl, oklch)
formatNoOutput format: markdown report + CSS, css only, json, or W3C tokensreport
harmonyNoSecondary/accent harmony relative to brandanalogous
neutralStyleNoNeutral tinting: 'tinted' (subtle brand tint, default), 'cool', 'warm', or 'pure' grayscaletinted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real value with output guarantees ('contrast-verified', 'guarantees WCAG AA/AAA text pairs', 'prevents dark-mode neon halation'), but it says nothing about determinism of the harmony/neutral choices or how the light and dark sets relate.

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?

Two sentences, front-loaded with the core action and scope, then the 60-30-10 allocation and quality guarantees. The nested parenthetical is dense but every clause carries information; minor tightening is possible but nothing is filler.

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 four well-documented parameters, full annotations, and no output schema, the description needs to convey the shape and quality bar of the result, and it largely does: a light+dark system split into 60/30/10 roles with verified contrast. It stops short of describing the report/CSS/token payload structure, which leaves a small gap.

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% and three of four parameters are enums with per-value descriptions, so the schema does the heavy lifting. The description reinforces the single-seed input and the light/dark output pairing but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 specific verb and a tightly scoped resource: 'Design a complete, contrast-verified Light + Dark UI color system from a single brand color.' The 60-30-10 breakdown makes the deliverable concrete, distinguishing it in spirit from generic siblings like generate_palette or generate_semantic_palette, though no sibling is named explicitly.

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 only implied: the tool is for building a full UI palette from one brand seed. There is no statement of when to prefer it over generate_palette, generate_semantic_palette, generate_material_theme, or check_palette_accessibility, and no prerequisites or exclusions are given.

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