Skip to main content
Glama

Match a reference swatch

bpj_palette_nearest_swatch
Read-onlyIdempotent

Rank a supplied palette by D65 CIE76 difference and report the closest swatch.

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": {
      "color": "<color>",
      "palette": "<palette>"
    },
    "name": "bpj_palette_nearest_swatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes
paletteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds the important computation method, D65 CIE76, and says it reports the closest swatch, but it does not describe tie handling, error behavior, or the form of the reported result.

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 front-loaded sentence with no filler. It states the ranking method and outcome efficiently.

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

Completeness3/5

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

For a simple two-parameter matching tool, the description covers the core operation and method. But with no output schema and 0% schema description coverage, it should also explain the expected input formats and what the reported closest swatch contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate for undocumented parameter details. It does not clarify that color is a six-digit hex string or that palette is a JSON array of hex colors, leaving key formatting requirements to the schema titles alone.

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?

The description states a specific verb and resource: rank a supplied palette by D65 CIE76 difference and report the closest swatch. It clearly conveys the core operation, though it does not explicitly distinguish this tool from sibling palette utilities.

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

Usage Guidelines3/5

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

Usage is implied by the operation: use this when you have a reference color and palette and need the nearest match. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives among the many sibling tools.

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.