Tonebook Palette

Compare supplied digital colors

compare_colors

Read-onlyIdempotent

Compare up to 12 supplied six-digit hex colors or standard color names with a portable selected palette. Unknown or ambiguous names request hex values. Return the nearest digital swatch with a fixed RGB rule and concise rationale. This does not assess skin, photos, fabrics or garments you own.

Input Schema

Name	Required	Description
`colors`	Yes
`palette_ref`	Yes
`analytics_opt_out`	No	Set true when the user asks not to measure Tonebook usage. Apply that choice to each subsequent Tonebook call. The tool works identically either way. No quiz answers or result content are logged.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`result`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / analytics_opt_out

Added value: +{
+  "description": "Set true when the user asks not to measure Tonebook usage. Apply that choice to each subsequent Tonebook call. The tool works identically either way. No quiz answers or result content are logged.",
+  "type": "boolean"
+}

First observedOct 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description adds real value by disclosing the 12-color cap, the hex-vs-name resolution behavior, and the output shape (nearest swatch via a fixed RGB rule plus rationale). The 'fixed RGB rule' itself is left undefined, keeping it from a 5.

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?

Four tight sentences ordered purpose → edge case → return → exclusion, with no filler. Front-loading is good; the phrasing 'Unknown or ambiguous names request hex values' is slightly awkward but still earns its place.

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?

With an output schema present, return values needn't be explained, and annotations cover safety. However, for the required palette_ref the description leaves the origin/format of the 'portable selected palette' unclear, which is the main gap an agent would hit when composing a call.

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 33% (only analytics_opt_out is documented in-schema). The description partially compensates by explaining that colors accepts either six-digit hex or standard names and by characterizing palette_ref as a 'portable selected palette,' but it never clarifies palette_ref's format, length bounds, or where the agent obtains it.

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?

Specific verb (compare) plus resource (supplied digital colors) with an explicit scope constraint: 'up to 12 supplied six-digit hex colors or standard color names with a portable selected palette.' The purpose is distinguishable from the palette/quiz siblings, though no sibling is named for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes a clear exclusion ('does not assess skin, photos, fabrics or garments you own') and an edge-case rule ('Unknown or ambiguous names request hex values'). It stops short of naming an alternative tool for the excluded cases or stating that palette_ref typically comes from select_palette, which is what a 5 would require.

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

All Tonebook Palette tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?