Generate harmonious color palettes from any hex color. 5 schemes: complementary, analogous, triadic, split-complementary, tetradic. Returns hex, RGB, HSL, and CSS vars.
Single tool 'design_generate_color_palette' has a well-structured schema with proper types and descriptions for all parameters. The tool description is comprehensive (280+ chars) and includes clear use cases, anti-patterns (what NOT to use it for), and output structure documentation. Parameter descriptions are specific ('Base hex color (e.g. #FF5733 or FF5733)') and include format guidance. However, the tool name lacks a clear action verb prefix, 'design_generate_color_palette' is awkwardly compound; 'generate_color_palette' would be clearer. Output schema is documented in the description but not formally in a separate schema block. Error handling and recovery guidance are absent from the definition.
Use this when you need to generate a harmonious color palette from a base hex color. Returns multiple color formats ready for design or code. 1. colors -- array of color objects, each containing hex, rgb (r,g,b), hsl (h,s,l), and cssVar 2. scheme -- the color scheme used (complementary, analogous, triadic, split-complementary, tetradic) 3. baseColor -- the input hex color 4. count -- number of colors in the palette Example output: {"colors":[{"hex":"#FF5733","rgb":{"r":255,"g":87,"b":51},"hsl":{"h":11,"s":100,"l":60},"cssVar":"--color-1: #FF5733;";}],"scheme":"complementary","baseColor":"#FF5733","count":5} Use this FOR building design systems, generating theme colors for websites, creating brand color guidelines, or picking accessible color combinations for UI components. Use this BEFORE starting any design project that needs a cohesive palette. Do NOT use for image processing -- use media_extract_text_from_image instead. Do NOT use for favicon generation -- use utility_generate_qr_code instead. Do NOT use for screenshot capture -- use capture_screenshot instead.
Tool name 'design_generate_color_palette' is compound and lacks a clear action verb. Should be 'generate_color_palette' (verb_noun pattern). The 'design_' prefix adds no semantic value and increases name length without clarity.
Output schema is documented only in the description text, not as a formal JSON Schema object. LLMs cannot reliably parse prose descriptions of response structures. Provide an explicit outputSchema with typed fields (colors array, scheme enum, baseColor string, count number).
No error handling or recovery guidance in tool definition. What happens if the hex color is invalid? If count exceeds 10? If the scheme is unrecognized? Tool should document error cases and guide the LLM on how to retry or correct input.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2025-06-18+ | v2 |
The 'scheme' parameter description lists valid values inline ('complementary, analogous, triadic, split-complementary, tetradic') but does not declare them as an enum in the schema. Enums are machine-parseable and prevent LLM hallucination of invalid schemes.
The 'count' parameter lacks explicit min/max constraints in the schema. Description says 'default: 5, max: 10' but no minimum is stated. Schema should declare minimum: 1, maximum: 10 to prevent LLM from passing invalid values like 0 or 100.