PickShade MCP Server

Convert a color

convert_color

Read-only

Convert colors between formats such as hex, RGB, HSL, OKLCH, CMYK, Display P3, and platform code (SwiftUI, UIKit, Flutter, Android).

Instructions

Convert a color between formats: hex, rgb, hsl, hsv, hwb, cmyk, lab, lch, oklab, oklch, display-p3, rec2020, xyz and platform code (swiftui, uikit, flutter, android). Values follow CSS Color 4.

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": "convert_color"
  }
}

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
`formats`	No	Formats to return. Defaults to hex, rgb, hsl, oklch, oklab and display-p3

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that values follow CSS Color 4, which is useful behavioral context about accepted syntax. It does not mention default formats beyond the schema, output shape, or error behavior, so it remains adequate rather than rich.

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?

Two sentences: one states the operation and format set, the second adds the CSS Color 4 standard. No waste, front-loaded, easy to scan.

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?

The tool is simple with only two params and full schema coverage, so the description is nearly sufficient. It could note the default format set or error conditions for invalid input, but those are minor omissions for a read-only conversion tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are fully documented in the schema, giving a baseline of 3. The description adds the format family list and the CSS Color 4 standard, which clarifies accepted value syntax beyond the schema's examples, nudging this to 4.

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 (convert) and resource (a color between formats), and enumerates the format set. Among siblings like parse_color, mix_colors, and check_gamut, this is clearly the format-transformation tool.

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 usage (you have a color and want other formats) but gives no explicit when-to-use vs. parse_color or check_gamut. Nothing routes the agent away from misusing this when it actually wants parsing or gamut checking.

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

Deploy Server