Skip to main content
Glama

Find equivalent paint colours in other brands

find_equivalents
Read-onlyIdempotent

Find the closest colours in OTHER brands to a given paint colour or hex value, e.g. "Behr equivalent of Farrow & Ball Hague Blue" or "which Benjamin Moore is closest to #D1CBC1". Give either brand + name_or_code, or hex. Distance is CIEDE2000 ΔE with a verdict: under 1 practically identical, under 2 very close, under 3.5 close, otherwise similar (nothing above ΔE 6 is returned). By default returns the single best match per brand, closest first; pass brands to restrict the search (with one brand you get several options from it). Always pass on the caveat that on-wall results depend on base, sheen and tinting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_equivalents"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexNoSource colour as hex, e.g. "#3D4E57" (instead of brand + name_or_code)
brandNoBrand of the source colour (with name_or_code)
limitNoMaximum results (default 8)
brandsNoOnly search these brands, e.g. ["Behr", "Sherwin-Williams"]
name_or_codeNoName or code of the source colour

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, and the description goes well beyond them: it discloses the CIEDE2000 ΔE metric, the verdict thresholds, the hard cutoff at ΔE 6, result ordering, and a required caveat to pass on to the user.

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?

Front-loaded with the purpose and examples, and every sentence carries information. It is a single dense block rather than being broken into scannable clauses, which slightly hurts readability but wastes no words.

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?

With no output schema, the description correctly takes on the burden of explaining return semantics (verdicts, ordering, per-brand default, cutoff). It omits edge cases such as what happens when no colour falls under ΔE 6 or when the source colour is not found.

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 the baseline is 3; the description adds real meaning on top by explaining the interaction between brands and result cardinality, and by describing the default one-best-match-per-brand behaviour that the schema's limit field alone does not convey.

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 and resource (find closest colours in OTHER brands) and anchors it with two concrete example queries, which makes it immediately distinguishable from get_paint_color and search_paint_colors.

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?

Gives clear input-mode guidance (either brand + name_or_code, or hex) and explains how the brands parameter changes result shape (one brand yields several options from it). It does not explicitly route the agent away from sibling tools, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources