Skip to main content
Glama

PaintDial

Find the closest paints

find_closest_paints
Read-onlyIdempotent

Find the UK paints closest in colour to a named paint or a hex value, across the 20 brands in the PaintDial library. For a named paint (for example "Hague Blue") it returns the closest colour from each other brand, as shown on that paint's PaintDial page. For a hex value (for example "#2F4858") it returns the closest paints from any brand. Each result has the brand, name, published colour value, a difference score, and a link to its PaintDial page.

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": {
      "colour": "<colour>"
    },
    "name": "find_closest_paints"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoOptional. With a paint name: the brand it belongs to, if the name is used by more than one brand. With a hex value: only return paints from this brand.
limitNoHow many matches to return. Default 5, maximum 10.
colourYesA paint name or code (for example "Hague Blue" or "No.30"), or a six-digit hex colour (for example "#2F4858").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description is free to add substance — and it does, by explaining the per-brand versus any-brand result semantics and listing the returned fields (brand, name, published colour value, difference score, page link). It does not cover failure behavior, such as an unrecognised paint name or an ambiguous name with no brand supplied.

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 core action and scope, then the two mode-specific behaviors, then the return shape. Every sentence carries information an agent needs; nothing is redundant with the name or title.

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 compensates by naming the fields each result contains, and it explains both input modes, which is enough to call the tool correctly. The remaining gap is edge-case behavior for unknown or ambiguous paint names.

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 schema already documents the dual role of "brand" and the default/maximum of "limit". The description adds no parameter-level detail beyond what the schema states, so the baseline 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?

"Find the UK paints closest in colour to a named paint or a hex value" gives a specific verb and resource, plus the scope (20 brands in the PaintDial library). It clearly separates the two lookup modes, but never names the sibling get_paint, so the agent must infer the boundary from the word "closest" rather than an explicit contrast.

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 for both input modes: a named paint yields one closest match per other brand, a hex value yields matches from any brand. It does not state when to prefer get_paint (exact paint details) over this tool, so the when-not guidance is absent.

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