Skip to main content
Glama

Check OKLab against sRGB gamut

bpj_oklab_srgb_gamut
Read-onlyIdempotent

Invert OKLab to linear RGB and test whether the coordinates fit within the sRGB gamut.

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": {
      "lightness": "<lightness>",
      "a": "<a>",
      "b": "<b>"
    },
    "name": "bpj_oklab_srgb_gamut"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
lightnessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the internal method (invert to linear RGB) but never says what the result looks like — a boolean, a per-channel report, or clipped values — which matters because there is 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.

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient, though the terseness leaves the return behavior unaddressed rather than being optimally structured for an agent.

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?

The tool is a simple three-scalar computation, so little context is strictly needed, and annotations cover side effects. However, with no output schema and no statement of the return value, the definition is not fully complete for correct invocation and interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; the schema supplies only titles and min/max bounds. The phrase 'OKLab coordinates' implicitly maps the three inputs to L, a, b, but the description adds no meaning about what out-of-range or boundary values mean or how the axes are interpreted.

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?

States a specific operation (invert OKLab to linear RGB, then test gamut membership) on a specific resource (sRGB gamut), which is distinguishable from the color-adjacent sibling bpj_color_contrast_check. It does not explicitly name a sibling it is not, so it stops 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, no mention of prerequisites or alternatives. An agent must infer from the name alone that this is the gamut-membership check rather than a conversion or contrast tool.

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.