Skip to main content
Glama

describe_color

Read-onlyIdempotent

Converts hex, CSS, RGB, HSL, or OKLCH colors into human-readable descriptions with temperature, lightness, vividness, text contrast guidance, UI roles, and visual pitfalls.

Instructions

Describe what one or more colors actually look like in human perceptual terms (name, warm/cool temperature, lightness & vividness tier, OKLCH/HCT/HSL/RGB values, readable text recommendation, UI role suggestions, and visual pitfalls like bile-zone or halation). Use this whenever you cannot 'see' a hex code.

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": {
      "colors": "<colors>"
    },
    "name": "describe_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsYesOne or more colors to describe (hex, CSS name, rgb, hsl, oklch)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety and determinism are covered. The description adds genuine value by enumerating the analysis dimensions returned (perceptual name, temperature, tier, pitfalls like bile-zone or halation), but says nothing about output structure, ordering matching input order, or the 20-color cap.

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?

Two sentences, front-loaded with the core action before the parenthetical output list. The parenthetical is long but each item is a distinct capability an agent needs to decide to call this; only the trailing 'use whenever' sentence could be trimmed slightly.

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

Completeness5/5

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

For a one-parameter, read-only computation tool with no output schema, the description carries the necessary burden by spelling out what analysis is returned and why it matters perceptually. Nothing an agent needs in order to call it correctly appears to be missing.

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 description coverage is 100% and the single parameter documents accepted formats (hex, CSS name, rgb, hsl, oklch) plus min/max items. The description only echoes 'one or more colors' and adds no format or batching guidance beyond the schema, so the baseline of 3 applies.

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?

Specific verb plus resource: it describes what colors 'actually look like in human perceptual terms' and enumerates the outputs (name, temperature, lightness/vividness tier, color-space values, text recommendation, UI role, perceptual pitfalls). That enumeration separates it from convert_color or check_contrast without naming them, so sibling differentiation is implied rather than stated.

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?

'Use this whenever you cannot see a hex code' gives an explicit triggering condition for when to reach for this tool. It offers no exclusions and does not name a concrete alternative for cases like 'I need only the RGB value' or 'I need a contrast verdict', which keeps it below a 5.

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