Skip to main content
Glama

OKLCH color coordinates

bpj_color_oklch
Read-onlyIdempotent

Transform linear sRGB into OKLab and report cylindrical lightness, chroma and hue.

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_color_oklch"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes

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 transform basis (linear sRGB) but says nothing about rounding precision, hue units, out-of-gamut handling, or what the reported values look like. With annotations carrying the behavioral bar, this is acceptable but thin.

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?

One front-loaded sentence with no filler; the transform is stated before the reported quantities. Slightly terse given the input-format ambiguity it leaves behind.

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 single-parameter pure conversion with no output schema, the description should at least pin down the input encoding and the shape of the returned lightness/chroma/hue values. It names the three reported components, which is useful, but leaves the hex-versus-linear-sRGB gap and output formatting unaddressed.

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% and the single parameter's meaning is not clarified by the description. Worse, the description frames the input as 'linear sRGB' while the schema demands a six-digit hex string with maxLength 7, leaving ambiguous whether the '#' prefix is expected and whether the value is linearized or plain sRGB. A brief format statement would have resolved both.

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 verb and resource: transform sRGB into OKLab and report cylindrical lightness, chroma and hue. That distinguishes it from the Lab D65 and XYZ siblings by naming the OKLCH output components. It never explicitly contrasts itself with those siblings, so the differentiation is implied rather than stated.

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 guidance at all — no mention of when OKLCH is preferable to the Lab, XYZ or HSL sibling tools, and no prerequisites or exclusions. The agent must infer selection purely from the tool name.

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.