Skip to main content
Glama
Sign In
grayscale-mcp

grayscale-mcp

by truefrontier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export palette code

export_palette
Read-onlyIdempotent

Exports color palettes as Tailwind, Radix, CSS variables, SCSS, Less, Stylus, auto-dark CSS/Tailwind, SVG, or JSON code for direct project use.

Instructions

Export palettes as the code the site's "Export Your Colors" and "Tailwind Auto-Dark Mode" sections produce: tailwind (theme colors object), radix (light + dark scales), css-vars, scss, less, stylus, auto-dark-css (CSS variables that flip in dark mode), auto-dark-tailwind (tailwind.config.js for those variables), svg (the "Export Svgs" swatch sheet) or json (raw swatch data).

Input Schema

NameRequiredDescriptionDefault
lumsNoCustom luminance targets (0-100, WCAG relative luminance x100), lightest first. Same as dragging the site sliders.
countNoNumber of shades (site +/- buttons, 3-20).
colorsNoBase colors, one palette each.
formatYesOutput format.
presetNoLuminance preset from the site menu: default (12 shades, 50-1100), tailwind (11 shades, 50-950), radix (12 steps), or bell/linear/dark/light which redistribute the current min..max range.
share_urlNoA grayscale.design/app?... share link to load instead of colors/lums.
color_typeNoColor notation for tailwind/radix/css-vars/scss/less/stylus. Site default: rgb.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover safety hints (readOnlyHint: true), but the description adds valuable structural context regarding the output, explaining things like 'Tailwind theme colors object' or 'raw swatch data.' This provides clarity on the result itself, augmenting the metadata provided by the annotations.

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 definition is presented as a single, comprehensive sentence. While long, it is highly efficient as every phrase contributes to defining the scope and nature of the export functionality.

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?

Given the complexity (7 parameters), the description defines the critical outcome—the output format—with high clarity. Since the input schema is 100% detailed, the description is complete enough to define the tool's capability without needing to elaborate on the parameters.

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?

Since the schema description coverage is 100%, the input parameters (lums, colors, etc.) are thoroughly explained in the schema. The description focuses exclusively on defining the *output formats* of the tool, adding minimal semantic value to the input parameters themselves. Baseline score is appropriate.

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?

The description is highly specific, stating that the tool exports palettes into nearly all major web development code formats (Tailwind, Radix, SCSS, etc.). This clearly defines the tool's function and distinguishes it from generators like suggest_colors.

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?

The description does not explicitly state when to use this tool versus siblings like generate_palette. However, by listing the specific output formats, it strongly implies that this tool is for final code generation rather than initial palette design, providing implied usage context.

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

Deploy Server

Other Tools