Skip to main content
Glama

Generate Chart Palette

generate_chart_palette

Generate colorblind-safe chart palettes—categorical, sequential, or diverging—with verification notes to keep data visualizations readable and accessible.

Instructions

Data-visualization colors that stay readable for everyone: a colorblind-safe categorical palette (up to 8), a sequential ramp from one color with steadily falling lightness, or a diverging palette with a neutral midpoint. Includes verification notes. Deterministic, no API key needed.

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_chart_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
lowNoDiverging only: color for the low end
baseNoSequential only: base color as hex
highNoDiverging only: color for the high end
kindNocategorical
countNo
formatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: deterministic output, no API key/auth requirement, and that the result includes verification notes. It stops short of stating what happens when diverging is requested without low/high, or how errors surface.

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 tight sentences: the value proposition and the three modes come first, then the practical constraints (verification notes, deterministic, no key). No filler and nothing buried.

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?

For a 6-parameter, annotation-free tool with no output schema, the definition covers purpose and mode selection adequately but leaves output shape (json vs css formatting), the count ceiling conflict, and mode-specific parameter requirements undocumented. An agent can call it, but not predict what it will get back.

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 only 50% (low, base, high are documented; kind, count, format are not), so the description should compensate. It partially does by tying modes to inputs (sequential from one color, diverging with a neutral midpoint), but it says the categorical palette holds "up to 8" while the schema allows count up to 11 – a discrepancy that leaves the agent guessing about the real limit, and format/count semantics are unexplained.

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 names a specific resource (chart/data-visualization palettes) and enumerates the three concrete modes it produces: colorblind-safe categorical, sequential ramp, and diverging with neutral midpoint. It is clearly not the generic palette generator, though it never names the sibling to route away from.

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?

"Data-visualization colors that stay readable for everyone" implies the use case (chart coloring with accessibility requirements) but gives no explicit when-to-use/when-not and no pointer to alternatives such as generate_palette or simulate_colorblind. Usage is left to inference.

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