Skip to main content
Glama

Palette against brief

colour_palette_brief_check
Read-only

Check a color palette against a brief. Give palette (hex, rgb() or hsl(), optionally named, up to 16) and optionally brief (words such as calm, energetic, premium, playful, trustworthy, natural, minimal, warm, cool). Returns measured properties, a verdict per brief word (supported, contradicted or untestable) with the measurement behind it, palette issues (too many colors, no neutral, near-duplicates, pairs that look alike under color-vision deficiency, no 4.5:1 text pair), and each color's contrast on white and black. Mood associations are common conventions and vary by culture.

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

Input Schema

NameRequiredDescriptionDefault
briefNoBrief words, comma or line separated
paletteYesPalette colors, optionally named, up to 16

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / palette / description
      Previous value: -"Palette colours, optionally named, up to 16"New value: +"Palette colors, optionally named, up to 16"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so safety is covered; the description adds substantive context beyond that: the exact verdict vocabulary (supported/contradicted/untestable), the enumerated issue classes, and the honest caveat that mood associations are cultural conventions. It does not state latency or input-validation failure behavior, which keeps it from a 5.

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 action, then inputs, then outputs, then a caveat – a sensible order. The enumerated issue list and brief vocabulary are dense but each item is informative; a couple of clauses could be trimmed without loss.

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?

With no output schema, the description takes on the burden of describing returns and does so thoroughly (measured properties, per-word verdicts with measurements, issue classes, white/black contrast). Combined with input formats and a scope caveat, an agent has everything needed to call it correctly.

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, and the description earns above baseline by adding color syntaxes (hex, rgb(), hsl()) and a concrete vocabulary of brief words that the schema does not provide. The 16-color cap and optional naming are repeated from the schema, but the added detail is real.

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?

States a specific verb+resource combination ('check a color palette against a brief') that is clearly narrower than siblings like palette_harmony or check_contrast. However it never names an alternative sibling to route against, so the differentiation is implicit rather than explicit.

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?

The description makes the usage scenario clear (you have an existing palette plus optional mood words) and enumerates the accepted brief vocabulary, so an agent can infer when it applies. It stops short of stating when not to use it or which sibling to pick for pure contrast or harmony checks.

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