Skip to main content
Glama

List the colors a theme uses

patchwork_palette
Read-onlyIdempotent

Lists a theme's colors as 6-digit hex values with frequency counts, most frequent first, so you can choose color-map keys for retheming or recoloring layouts.

Instructions

List the colors a theme uses, as the theme name then one line per 6-digit hex color with its count, most frequent first. Use it to choose the keys of the colors map of patchwork_retheme or patchwork_recolor_layouts.

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

Input Schema

NameRequiredDescriptionDefault
themeNoDisplay or internal name of the theme. Default: the theme most layouts use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds real context beyond that by disclosing the return layout and sort order (most frequent first) even though no output schema exists. It does not mention size limits or whether all themes' colors are ever truncated, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste. The output contract is front-loaded in the first sentence and the usage routing in the second, so an agent gets the essentials immediately.

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?

For a single-optional-parameter read tool with no output schema, the description supplies the two things that matter most: the exact result format and where the result feeds into. Nothing needed to call it correctly is missing.

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%: the single 'theme' parameter is already documented in the schema, including its default of the theme most layouts use. The description adds no further semantics about the parameter, so the baseline 3 applies.

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 gives a specific verb and resource ('List the colors a theme uses') and even specifies the output shape: theme name followed by one line per 6-digit hex color with its count, most frequent first. It stops short of explicitly contrasting itself with other listing siblings such as patchwork_uses or patchwork_show, but the scope is unambiguous.

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?

It tells the agent exactly when to reach for it: to choose the keys of the colors map for patchwork_retheme or patchwork_recolor_layouts. That is a clear forward reference to the consuming tools. There is no explicit when-not guidance, but the narrow scope makes misuse unlikely.

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