Skip to main content
Glama

analyze_palette_consistency

Read-onlyIdempotent

Score a color palette's visual cohesion with a 0-100 rating, tonal step/chroma/hue diagnostics, and targeted suggestions for improving consistency.

Instructions

Score how visually cohesive a palette is. Reports tonal step uniformity, chroma spread, hue distribution, and a single 0-100 cohesion score, plus targeted suggestions for tightening it up.

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

Input Schema

NameRequiredDescriptionDefault
colorsYesPalette colors to analyze (2-64)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description does not need to cover safety. What it does add is the return shape — four named metrics, a 0-100 cohesion score, and actionable tightening suggestions — which matters because there is no output schema to fall back on. It stops short of saying anything about determinism or how suggestions are ranked.

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?

Two sentences, no filler, and the core purpose is front-loaded before the enumeration of outputs. Every clause carries information the agent needs.

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?

Given one simple parameter and no output schema, the description carries the burden of explaining what comes back, and it does so concretely (metrics, score scale, suggestions). Minor remaining gap is that it does not characterize the input color format or how the score should be interpreted qualitatively.

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, 'colors', and schema coverage is 100% with an inline description of 'Palette colors to analyze (2-64)' plus minItems/maxItems. The description adds no format guidance (hex vs named colors) beyond the schema, so the baseline 3 applies.

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 ('Score how visually cohesive a palette is') and then enumerates the exact dimensions measured (tonal step uniformity, chroma spread, hue distribution). That enumeration is what separates it from siblings like analyze_color_likability and check_palette_accessibility 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 Guidelines3/5

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

Usage is only implied: the tool analyzes a palette you already have and reports cohesion. There is no explicit when-to-use framing, no stated prerequisite (e.g. minimum palette size or what makes a palette a candidate for this analysis), and no pointer to the generate_* or check_palette_accessibility alternatives.

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