PickShade MCP Server

Generate a palette

generate_palette

Read-only

Create a harmonious OKLCH color palette from a seed or colors you keep; pick a style like analogous or pastel to get repeatable results.

Instructions

Generate a harmonious palette in OKLCH. Keep colors you already have, pick a style (auto, analogous, complementary, triadic, monochromatic, pastel, vivid, muted, dark) and pass a seed to get the same palette every time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_palette"
  }
}

Input Schema

Name	Required	Description	Default
`keep`	No	Colors that must stay in the palette, in order
`mode`	No		auto
`seed`	No	Any text. The same seed gives the same palette
`size`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful behavioral detail: the deterministic seed behavior ('pass a seed to get the same palette every time') and that 'keep' colors are preserved. However, it doesn't describe output format or the meaning of the mode styles beyond naming them.

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?

One efficient sentence that front-loads the core purpose (generate a harmonious palette in OKLCH) and packs the parameters into a compact clause. Slightly dense but nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with no output schema and no annotations conflict, the description covers the essentials but omits output shape, what the 'auto' mode does, and how 'size' interacts with 'keep'. Adequate but with clear gaps given no output schema to carry return-value documentation.

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 coverage is 50%, with 'keep' and 'seed' well-documented in the schema but 'mode' and 'size' lacking descriptions. The description names the mode options (matching the schema enum) and re-states the seed determinism, but adds no semantics not already in the schema. Baseline 3 given the mixed coverage.

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 (harmonious palette in OKLCH), and lists the modes and seed behavior. It's clearly distinguishable from siblings like generate_scale, harmonies, or tint_shades because it's the palette generator with a mode/style system.

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 implies when to use it (generating a new palette, optionally preserving existing colors via 'keep'), but doesn't explicitly say when to use generate_palette vs siblings like generate_scale or harmonies, nor any prerequisites. Usage is implied rather than stated.

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

Deploy Server