Skip to main content
Glama

generate_tonal_palette

Read-onlyIdempotent

Generates a Material Design tonal palette from a base color, with optional custom tone values from 0-100, to support accessible UI color systems.

Instructions

Generate a Material Design tonal palette from a color

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": {
      "color": "<color>"
    },
    "name": "generate_tonal_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYesBase color for palette
tonesNoCustom tone values 0-100 (default: Material standard tones)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description adds nothing beyond that: it does not say how many tones are returned by default, what format the output takes, or what happens when 'tones' is omitted. With annotations carrying the safety profile, this leaves the description with essentially no additional behavioral value.

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?

A single efficient sentence with no wasted words; the purpose is front-loaded. It is arguably under-specified rather than over-long, but on structure and economy it scores well.

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

Completeness3/5

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

This is a simple deterministic single-input tool with full schema coverage and complete annotations, so little narrative is strictly required. The remaining gap is output shape: without an output schema, the description should say roughly what a tonal palette looks like (a list of tones/hex values). Adequate but with a clear gap.

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%, with 'color' and 'tones' both documented in the schema including the 0-100 range, 32-item cap, and the default-standard-tones note. The description mentions only 'from a color' and adds no format hints (e.g. hex vs RGB input) beyond the schema. Baseline 3 is appropriate where the schema does all the work.

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 and resource: 'Generate a Material Design tonal palette from a color'. This is clear enough for an agent to know it produces a tonal palette rather than a categorical or semantic one. It does not, however, distinguish itself from the very similar sibling generate_tonal_scale.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as generate_tonal_scale or generate_material_theme. An agent must infer selection from the name alone, which is risky given the crowded sibling set of palette generators.

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