Skip to main content
Glama

Tint and shade scale

tint_shade_scale
Read-only

Generate a 50, 100, 200 ... 900, 950 scale from one color (hex, rgb(), hsl() or a CSS name) and optionally a name for the CSS variables. Your color is kept exactly on the step nearest its own lightness; other steps follow a fixed OKLCH lightness curve with the hue held and chroma tapering toward the ends (reduced where sRGB cannot hold it). Each step reports hex, oklch(), WCAG contrast against white and against black, and whether it passes 4.5:1 as text on each. Also returns the lightest step that passes as text on white, the lightest that passes as text on black, any step that passes both, and a CSS custom-property block. Contrast is WCAG 2.x relative luminance.

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": "tint_shade_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name for the CSS variables, such as blue.
colorYesBase color, such as #2f6fed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / color / description
      Previous value: -"Base colour, such as #2f6fed."New value: +"Base color, such as #2f6fed."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds substantial behavior beyond that: the base color is pinned to the nearest lightness step, other steps follow a fixed OKLCH lightness curve with hue held and chroma tapered where sRGB cannot hold it, and contrast is WCAG 2.x relative luminance. This tells an agent exactly what transformations to expect and why some steps may deviate.

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?

Front-loaded with the core action and parameter forms in the first sentence; subsequent sentences are dense but every claim (curve behavior, per-step reporting, derived summaries, WCAG version) is load-bearing. The final enumeration of returned artifacts is slightly long but not padded.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so thoroughly: per-step hex/oklch()/contrast pairings, pass flags, lightest-passing-on-white and on-black, any dual-passing step, and a CSS custom-property block. Nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by enumerating the accepted color syntaxes (hex, rgb(), hsl(), CSS name) — the schema only shows '#2f6fed' as an example — and by explaining that `name` becomes the CSS custom-property prefix. That is meaningful added semantics.

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 resource (a 50–950 tint/shade scale) plus the exact input forms accepted. This is clearly distinguishable from siblings like modular_scale, build_spacing_scale, and palette_harmony without opening any schema.

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 strongly implied by the 'one color in, nine-step scale out' framing, but the description never states when to prefer this over check_contrast, check_contrast_tokens, or palette_harmony, nor any exclusions. An agent must infer the routing decision from the tool name and output shape.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources