Skip to main content
Glama

generate_color_palette

Read-onlyIdempotent

Generate a 5-stop HSL color palette from a base hex and chosen harmony, with WCAG 2.1 contrast ratios against dark and light surfaces for accessible UI design.

Instructions

Generate a 5-stop HSL color palette with WCAG 2.1 contrast ratios against dark and light surfaces.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_color_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
harmonyNocomplementary
base_hexNo#00e5ff

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds real behavioral content beyond them by disclosing the output composition (5 stops, HSL) and that contrast is computed against both dark and light surfaces. It does not say whether output is deterministic for a given input or how the default base color is chosen, which keeps it off 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler and the key output constraint front-loaded, which is close to ideal in structure. However, given two undocumented parameters, the extreme brevity is partly the source of the definition's gaps rather than pure economy.

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

Completeness2/5

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

For a two-parameter generator with no output schema and 0% schema description coverage, the definition should explain what each parameter does and roughly what comes back. It sketches the return content but leaves both parameters, default behavior, and the output structure undocumented.

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 0%, so the two parameters (harmony enum, base_hex) carry no documented meaning anywhere except their names and the enum values. The description mentions HSL output while the input is a hex string, which is unremarked and mildly confusing, and it never mentions the harmony concept at all.

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 (Generate) and a precisely characterized resource (5-stop HSL color palette with WCAG 2.1 contrast ratios against dark and light surfaces). No sibling in the catalog produces palettes, and the description makes the output shape unmistakable, so an agent can distinguish it without opening the schema.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative guidance; the only context is the implied accessibility/palette-generation domain. An agent must infer that this is the tool for design-token or theme color work rather than being told.

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