Skip to main content
Glama
Colors MCP Server

Colors MCP Server

by HtetOoWaiYan

Describe or validate colors

colors_info
Read-onlyIdempotent

Validate color strings and describe each in hex, RGB, HSL, OKLCH, closest CSS name, lightness, sRGB fit, and white/black contrast to choose text color.

Instructions

Validate color strings and describe each: hex, rgb, hsl, oklch, closest CSS name, how light it is, whether it fits sRGB, and contrast against white and black (so you can pick black or white text). Use to check that an input is a real color, or to understand an unfamiliar color. Bad inputs are reported per color, with a suggestion.

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

Input Schema

NameRequiredDescriptionDefault
colorsYesColors to describe or validate. A list, even for a single color. Any CSS color strings.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: invalid entries are reported per color with a suggestion, implying partial-success batch semantics rather than all-or-nothing failure. It says nothing about ordering, cost, or limits on the batch size.

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?

Three sentences, front-loaded with the action, then the payload, then the use cases and error behavior. No clause is filler; the parenthetical about black/white text picks explains why contrast is reported.

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 single-parameter, annotation-covered, output-schema-bearing tool, this covers purpose, inputs, use cases, and failure reporting. Nothing needed to call it correctly is missing, and the return-field enumeration is a bonus rather than a redundancy.

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?

There is a single parameter at 100% schema description coverage, so the schema already explains that it takes a list of any CSS color strings, even for one color. The description adds no format details, accepted color-space list, or handling nuance beyond what the schema states, so baseline 3 is correct.

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 concrete verb pair (validate, describe) against a specific resource (color strings) and then enumerates exactly what each entry yields: hex, rgb, hsl, oklch, closest CSS name, lightness, sRGB fit, and contrast versus white/black. That enumeration separates it from conversion- or comparison-oriented siblings without needing to name them.

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?

Explicitly gives two triggering situations: checking that an input is a real color, and understanding an unfamiliar color. It does not name exclusions or point to a specific alternative sibling, so it falls short of a full when/when-not routing statement.

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