Skip to main content
Glama

generate_semantic_palette

Read-onlyIdempotent

Generate a full semantic palette from one brand color, including primary, secondary, tertiary and status colors, with tone and chroma normalized in HCT space so all colors feel related.

Instructions

From a single brand color, generate a complete visually-cohesive semantic palette: primary, secondary, tertiary, plus success/warning/error/info status colors. Tone and chroma are normalized in HCT space so every color feels like part of the same family.

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": {
      "brand": "<brand>"
    },
    "name": "generate_semantic_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand / seed color (hex, rgb, hsl)
isDarkNoGenerate the palette for a dark theme background

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the normalization happens in HCT space and the intent is cross-color family cohesion, which tells the agent the output is deterministic and internally harmonized rather than arbitrary. It stops short of describing the return shape (map vs array), which matters slightly since there is no output schema.

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, front-loaded with the transformation and followed by the output inventory and the harmonization rationale. No filler, no restatement of the tool name.

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?

For a two-parameter pure function with full schema coverage and complete annotations, the description covers input, output composition and the harmonization guarantee. The only real gap is the concrete return structure, which the agent must discover by calling it since no output schema exists.

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%, so both parameters are already documented, including accepted formats (hex, rgb, hsl) and the isDark default. The description reinforces the single-seed nature of 'brand' but says nothing about isDark or dark-theme behavior, so it adds little beyond the schema – baseline 3.

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 gives a specific verb and resource ('generate a complete ... semantic palette') and enumerates the exact outputs: primary, secondary, tertiary plus success/warning/error/info. That output enumeration implicitly separates it from siblings like generate_categorical_palette or generate_tonal_palette, but no sibling is named explicitly, so an agent still has to infer the routing.

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 by the input condition 'From a single brand color' – an agent can infer this is the seed-color-driven semantic generator, but there is no explicit when-to-use, when-not, or pointer to the categorical/tonal alternatives in the sibling list.

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