PickShade MCP Server

Mix two colors

mix_colors

Read-only

Blend two colors at a chosen ratio and color space, such as OKLab or sRGB, to control midpoint brightness. Returns the mixed color and a CSS color-mix() expression.

Instructions

Mix two colors at a ratio in a chosen color space, like CSS color-mix(). OKLab keeps the middle bright, sRGB tends to turn gray. Returns the result and a ready color-mix() expression.

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": {
      "first": "<first>",
      "second": "<second>"
    },
    "name": "mix_colors"
  }
}

Input Schema

Name	Required	Description	Default
`first`	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
`space`	No		oklab
`amount`	No	Share of the second color in percent
`second`	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.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so safety is covered. The description adds valuable behavioral context: OKLab keeps the middle bright while sRGB tends to turn gray, and it returns a ready color-mix() expression. This exceeds bare annotation coverage, though it doesn't discuss error handling or edge cases.

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 description is two concise sentences that front-load the core purpose and add a useful color space note. It avoids redundancy, though the color space behavioral note could be more tightly integrated.

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 tool's simplicity (4 params, no output schema), the description covers purpose, a key behavioral nuance, and return format. It's nearly complete, but lacks usage guidelines against sibling tools, which is a minor gap.

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 75%. The description mentions 'at a ratio' and 'in a chosen color space,' which maps to the amount and space parameters, but it doesn't clarify that amount is the share of the second color, nor does it enumerate acceptable color formats beyond what the schema already describes.

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 states a specific verb (Mix) and resource (two colors) with the ratio and color space dimensions, making the tool's function immediately clear and easily distinguishable from siblings like convert_color or 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?

It implies the tool is for blending colors but provides no explicit guidance on when to use it versus alternatives like convert_color or find_colors, nor any prerequisites or exclusions.

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

Deploy Server