Skip to main content
Glama

Order a palette by lightness

bpj_palette_lightness_order
Read-onlyIdempotent

Sort palette swatches by perceptual OKLab lightness and return their coordinates.

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": {
      "palette": "<palette>"
    },
    "name": "bpj_palette_lightness_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
paletteYes

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?

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered elsewhere. The description adds that output is coordinates rather than the sorted swatches, which is genuinely useful, but it omits sort direction (ascending vs descending), whether the input palette is echoed or replaced, and what exactly a 'coordinate' contains.

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 well-formed sentence that front-loads the action and sort criterion. Nothing is wasted, though there is little structure to hang extra detail on.

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 single-parameter utility this is close to adequate, and the annotations carry the safety story. However, with no output schema, the vague 'return their coordinates' leaves the response shape (OKLab triplets? hex plus L?) and sort direction underspecified.

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?

Only one parameter with 0% schema description coverage; the schema only labels it 'Hex color array (JSON)' with a 1500-char cap. The description's 'palette swatches' loosely confirms the input is a color set but adds no format, ordering-of-input, or length guidance to compensate for the coverage gap.

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 (sort) + resource (palette swatches) + explicit sort key (perceptual OKLab lightness), plus a return statement. It is clearly distinguishable from siblings like bpj_palette_nearest_swatch or bpj_palette_css_variables, though no sibling is named to reinforce the boundary.

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?

No when-to-use or when-not-to-use guidance, and no alternative named. The agent must infer that this is the ordering counterpart to the other palette tools purely from the name and description.

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.