Skip to main content
Glama

generate_tonal_scale

Read-onlyIdempotent

Build a perceptually even 50–950 tonal scale from a seed color to create shadable design-system colors and CSS variables.

Instructions

Generate a complete tonal scale (Tailwind-style 50/100/.../900/950) from a seed color. Uses Google's HCT color space so each step is perceptually even — ideal for building shadable design-system colors.

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": {
      "seed": "<seed>"
    },
    "name": "generate_tonal_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCSS variable base name (default: 'color')
seedYesSeed color (hex, rgb, hsl)
stopsNoCustom stops. Default: [50,100,200,300,400,500,600,700,800,900,950].
chromaBoostNoMultiplier on seed chroma (1 = preserve, <1 = muted)

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 readOnly/idempotent/non-destructive, so the safety bar is met structurally. The description adds real behavioral context beyond that: the HCT color space and the guarantee that steps are perceptually even, which tells the agent the character of the output. It still omits the exact return shape (token/value pairs), though the color space note is a substantive addition.

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 dense sentences with the primary action and output shape front-loaded, then the technical rationale. No filler or redundancy; the em-dash clause earns its space by explaining why the scale is even.

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 four-parameter, single-operation generation tool with full schema coverage and no output schema, the description covers purpose, technique, and intended use. The return value is only implied (via "CSS variable base name"), which is a minor remaining 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 description coverage is 100%, so all four parameters (including stops, name, and chromaBoost) are already documented in the schema. The description adds the "seed" framing and echoes the default 50-950 stop ladder but no syntax or format detail beyond it, so the schema carries the load.

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?

"Generate a complete tonal scale ... from a seed color" gives a specific verb plus resource and pins the output shape (Tailwind-style 50/100/.../900/950), so it is not a tautology. It does not explicitly contrast with the sibling generate_tonal_palette, leaving the agent to infer the tonal-scale vs. general-palette distinction.

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?

"Ideal for building shadable design-system colors" is a usage hint that implies when this tool fits. But there is no explicit when-not, no prerequisites, and no named alternative for palette generation, so guidance stays implied rather than directive.

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