Skip to main content
Glama

generate_categorical_palette

Read-onlyIdempotent

Generate perceptually balanced, color-blind-safe categorical colors for charts, badges, tags, or avatars, optimized to keep categories distinct under normal and color-vision-deficient sight.

Instructions

Generate N perceptually balanced, color-blind-safe categorical colors for charts, badges, tags, or avatars. Optimizes minimum ΔE2000 across normal vision AND protanopia/deuteranopia/tritanopia so no category vanishes or collides.

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": {
      "count": "<count>"
    },
    "name": "generate_categorical_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of distinct categories (2-12)
seedColorNoOptional brand/anchor color to start the categorical spread from
backgroundNoTarget canvas polarity ('light' or 'dark')light

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world operation, so the burden is lower. The description still adds substantive behavior the annotations cannot convey: the output is optimized for minimum ΔE2000 across normal vision AND protanopia/deuteranopia/tritanopia, which tells the agent the quality guarantee behind the result. It stops short of stating determinism for a repeated call or what the response payload looks like.

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 tight sentences with zero filler; the core action and use cases come first and the optimization guarantee second. Every clause carries information an agent can act on.

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 and only three simple parameters, the description covers purpose, use cases, and the underlying optimization criterion well. The remaining gap is the return shape — presumably a list of hex values — which is never stated, so the agent cannot fully anticipate the response.

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 coverage is 100% and all three parameters are described in the schema, so the baseline is 3. The description reinforces that the output is a distinct-category spread and that no categories collide, but adds no new syntax, format, or constraint information beyond what the schema already states for count, seedColor, and background.

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 opens with a specific verb+resource ('Generate ... categorical colors') and adds concrete qualifiers — perceptually balanced, color-blind-safe — plus named use cases. It implicitly separates itself from generic palette siblings by stressing categorical usage and worst-case separation, but never names an alternative, so an agent must infer the boundary itself.

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?

Use cases ('charts, badges, tags, or avatars') give implied context for when this tool fits, which is more than nothing. However, there is no explicit when-not guidance and no reference to sibling tools such as the sequential/tonal or semantic generators, leaving the agent to guess at the categorical-vs-other distinction.

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