Skip to main content
Glama

Get a palette

get_palette

The colours of a built-in palette (e.g. pico-8, game-boy-dmg, cga-16, ega-64), as hex codes or a GIMP/Aseprite .gpl file.

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": {
      "id": "<id>"
    },
    "name": "get_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPalette id, e.g. "pico-8" (see list_palettes)
formatNohex: one line of #RRGGBB codes; gpl: a GIMP/Aseprite palette filehex

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the important behavioral trait that output shape depends on format (a single line of hex codes versus a full GIMP/Aseprite .gpl file). It says nothing about error behavior for an unknown id, or whether the palette is a static built-in constant, which matters for a no-annotation tool.

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?

A single tight sentence with zero filler, and the concrete palette examples are placed where they help. It is slightly awkward as a fragment rather than a sentence with a verb, but nothing is wasteful.

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

Completeness4/5

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

For a two-parameter read tool with full schema description coverage and no output schema, the description conveys enough: what is returned, in what forms, and which palettes qualify. The main missing piece is guidance on what happens for an invalid built-in id or how to discover valid ids from the description itself.

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%, so the enum values and id format are already documented; the description's mention of 'hex codes or a GIMP/Aseprite .gpl file' mostly restates the format parameter. The example id list adds mild value for the id parameter, but nothing beyond what the schema already provides.

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 definition names the resource concretely ('the colours of a built-in palette') and lists example ids (pico-8, game-boy-dmg, cga-16, ega-64), which makes it distinguishable from siblings like extract_palette or search_palettes by scoping it to built-ins. It lacks an explicit verb (it reads as a noun phrase describing the return value) and never names the sibling it contrasts with, so it falls just short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance in the description; the only routing clue ('see list_palettes') lives in the parameter schema, not the description. An agent must infer from the word 'built-in' that this is for predefined palettes rather than palettes extracted from an image.

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.