Skip to main content
Glama

Search palettes

search_palettes

Find built-in palettes by name and/or exact number of colours.

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

Input Schema

NameRequiredDescriptionDefault
queryNoPart of a name or id, e.g. "game boy" or "cga"
colorsNoOnly palettes with exactly this many colours

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it only adds the scoping detail that results are "built-in" palettes. It says nothing about match semantics (partial vs exact name, case sensitivity), what happens when both optional parameters are omitted, result ordering, or limits.

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?

A single short sentence with the action and both filter criteria front-loaded and no redundant wording. Nothing could be trimmed without losing content.

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 simple two-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. It still leaves open the zero-argument behavior and whether returned palettes can be fed into get_palette or remap_palette, which would matter to an agent chaining calls.

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 both parameters (query, colors) are already documented with examples and bounds, setting the baseline at 3. The description's "and/or" hints that the filters are independently optional and combinable, but adds no further meaning beyond the schema.

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 verb and resource ("Find built-in palettes") plus the two filter dimensions, so an agent can tell it is a filtered search rather than a plain listing. It does not explicitly contrast itself with list_palettes or get_palette, leaving sibling differentiation to inference.

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?

"by name and/or exact number of colours" implies when the tool is appropriate (filtered lookup), but there is no explicit statement of when to prefer list_palettes or get_palette instead. Usage is only implied by the filter phrasing.

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