mcp-ink-design

Overview Schema Source Related Servers Discussions Admin

Generate OKLCH Color Palette & Design Tokens

ink_generate_palette_tokens

Read-onlyIdempotent

Generate WCAG AAA-compliant OKLCH color ramps and fluid typography scales for design systems, with layered shadow elevations and ready-to-use CSS variables.

Instructions

PURPOSE: Generate bespoke OKLCH color token ramps, layered shadow elevations, and fluid clamp() typography scales tailored to a creative aesthetic mood and base hue.

BEHAVIOR: Synthesizes CSS custom property tokens and typography steps purely in-memory. Zero filesystem writes and zero external network access. Guarantees WCAG AAA contrast compliance across all text/surface pairings with mathematical delta-E verification.

USAGE GUIDELINES:

When to use: Use when creating or refining a design system's color foundation, fluid typographic scales, or dark/light mode surface tokens.
When NOT to use: Do NOT use to extract colors from an existing live website (use ink_inspect_website_style instead) or to scaffold an entire project skeleton (use ink_create_base instead).
Alternatives: Use ink_inspect_website_style to reverse-engineer design tokens from existing sites; use ink_create_base for full-page scaffolding.

RETURNS: ResultEnvelope containing semantic OKLCH token map, computed contrast analysis, fluid typography scales, and a ready-to-use CSS :root variable stylesheet string.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mood`	No	Creative aesthetic mood determining surface depths, text luminance steps, and brand accents	editorial
`baseHue`	No	Optional hue angle (0-360) on OKLCH color wheel (e.g., 210 for cyan, 260 for indigo, 30 for warm bronze, 145 for emerald)
`includeTypography`	No	When true, calculates fluid clamp() typography scale tokens (steps -1 through 5)
`includeArabicTokens`	No	When true, includes Arabic line-height ratios (1.7-1.85) and font fallback variables

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Domain-specific typed payload returned by the tool
`status`	Yes	Execution outcome status
`summary`	Yes	Concise, human-readable executive summary of the tool outcome
`evidence`	No	Audit trail, source references, and generated artifact locations
`warnings`	Yes	Operational cautions, craft advice, or non-blocking warnings
`nextActions`	No	Actionable sequential recommendations or subsequent tool suggestions

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.0Sep 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description goes further by adding 'Zero filesystem writes and zero external network access' and 'Guarantees WCAG AAA contrast compliance with mathematical delta-E verification', giving the agent concrete behavioral expectations beyond the structured hints. No contradiction.

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?

Well-structured with labeled sections (PURPOSE, BEHAVIOR, USAGE GUIDELINES, RETURNS), front-loaded with purpose, and each sentence adds value. No redundant phrasing or padding.

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 an output schema exists and annotations cover safety, the description still provides a concise return summary, explicit usage guidance, and behavioral guarantees. All necessary information for correct invocation and selection is present.

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 baseline is 3. The description mentions 'base hue' and 'mood' but does not add parameter-specific details beyond the schema's own descriptions. It adequately supports the schema without redundancy.

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 (generate) and resource (OKLCH color palette & design tokens), and explicitly distinguishes from siblings by naming what it is not for (extracting colors from live websites, scaffolding projects). The purpose is clear and actionable.

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

Usage Guidelines5/5

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

Contains explicit 'When to use' and 'When NOT to use' sections, plus named alternatives (ink_inspect_website_style, ink_create_base). This leaves no ambiguity about selection criteria and provides direct routing to siblings.

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

Deploy Server