PickShade MCP Server

Find colors by name

find_colors

Read-only

Search color names by keywords in English or Russian and return HEX values. Convert descriptions such as 'sage' or 'midnight blue' into usable colors.

Instructions

Search color names by words, like "sage", "dusty rose", "midnight blue" or "бордовый", and get their HEX values. Searches common names in English and Russian and about 30 000 extended color names. Use it to turn a description into real colors.

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": {
      "query": "<query>"
    },
    "name": "find_colors"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	Words to look for in color names
`locale`	No	Language for color names	en

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With annotations readOnlyHint=true and openWorldHint=false, the safe, closed-world read nature is already declared. The description adds the search scope (English, Russian, 30k extended names) but doesn't disclose other behavioral traits like rate limits or exact return format. It's adequate given 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the core purpose and supporting details without any redundancy or fluff.

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 has no output schema and only 3 parameters with 67% schema coverage, the description provides enough context about what it searches and returns (HEX values). It could mention the limit/result format, but otherwise it's sufficient for an agent to call it correctly.

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 description coverage is 67%, so some parameters (limit, locale) lack schema descriptions. The description mentions searching in English and Russian, which adds meaning to the 'locale' parameter. Examples like 'sage' clarify the 'query' parameter. This compensates for the coverage gap.

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 provides a specific verb ('search') and resource ('color names'), and distinguishes itself from the sibling 'nearest_names' by focusing on searching names by keywords rather than finding closest names to a color. It explicitly states it returns HEX values, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use it to turn a description into real colors, with examples like 'sage' or 'бордовый'. It implies the tool is for name-based lookup, but does not explicitly state when to use alternatives like 'nearest_names' or 'parse_color'.

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

Deploy Server