PickShade MCP Server

Generate a 50–950 scale

generate_scale

Read-only

Build an 11-step tint and shade scale from one color in OKLCH, matching Tailwind palette shape with even perceived lightness steps.

Instructions

Build an 11-step tint and shade scale (50, 100 … 900, 950) from one color in OKLCH, the same shape as Tailwind palettes, with even perceived lightness steps.

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": {
      "color": "<color>"
    },
    "name": "generate_scale"
  }
}

Input Schema

Name	Required	Description	Default
`color`	Yes	Any color: #ff5733, rgb(255 87 51), hsl(11 100% 60%), oklch(68% 0.21 34), a CSS or common name like navy, or a Tailwind class like sky-500

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral detail beyond them by naming the color space (OKLCH), the interpolation goal (even perceived lightness steps), and the exact output shape. It stops short of describing error handling for unparseable colors or the return format of each step.

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?

One sentence that front-loads the action and output, then qualifies it with color space and intent. No filler, no redundancy with the title.

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?

There is no output schema, so the description carries the burden of explaining results, and it does so adequately by specifying the 11 stop values and Tailwind-like shape and by disclosing the OKLCH/lightness rationale. Minor gap: it does not say what concrete value type is returned per step (hex, object, token name).

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?

With a single parameter and 100% schema description coverage, the schema already exhaustively documents accepted color formats with examples, so the baseline is 3. The description only reinforces that a single seed color is expected and adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource: build an 11-step tint/shade scale from one color, with explicit stop values (50, 100 … 900, 950) and the Tailwind-palette shape. It is clearly a single-input scale generator, though it never names or contrasts the closest siblings (tints_shades, generate_palette).

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 'from one color' phrasing implies when this tool applies (single-seed scale generation), but there is no explicit when-not guidance nor any named alternative such as generate_palette or tints_shades. Usage must be inferred from the input requirements.

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

Deploy Server