Skip to main content
Glama

Preview RGB565 quantization

bpj_rgb565_preview
Read-onlyIdempotent

Quantize a swatch for a 16-bit RGB565 display and preview the decoded color.

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": {
      "color": "<color>"
    },
    "name": "bpj_rgb565_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the substantive behavior — lossy 16-bit quantization followed by decoding back to a visible color — which tells the agent the result may differ from the input. It does not state what the response contains (quantized hex, error/delta, side-by-side swatch), leaving a gap for a tool with no output schema.

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 front-loaded sentence with no filler; the quantize action comes first and the preview outcome second. Nothing could be removed without losing information.

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 one-parameter, side-effect-free computation the description covers the essence, but with no output schema the agent still cannot predict the return shape or whether a diff/error metric is included. Given the tool's simplicity this is an adequate rather than complete definition.

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 exists and schema description coverage is 0%, though the schema does carry a title ("Six-digit hex color") and maxLength 7. The description's word "swatch" adds no format detail — it does not confirm the expected #RRGGBB form, case sensitivity, or whether the leading hash is required. A short format hint would have compensated 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?

The description uses a specific verb ("Quantize") with a specific target ("a swatch for a 16-bit RGB565 display") plus a second action ("preview the decoded color"). This is far more informative than a tautology and clearly identifies the resource and transformation, though it does not explicitly distinguish itself from the sibling preview tools by name.

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?

Usage is only implied: an agent can infer this is for checking how a color survives RGB565 quantization. There is no statement of when to prefer it over other preview siblings or any preconditions, but the domain is narrow enough that the implied context is unambiguous.

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.