Skip to main content
Glama

Luminance unit converter

bpj_units_luminance
Read-onlyIdempotent

Convert screen and emitting surface luminance. Enter one of cd/m2, kcd/m2, stilb, lambert, ft-L to return the equivalent value in every listed unit.

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": {
      "value": "<value>",
      "unit": "<unit>"
    },
    "name": "bpj_units_luminance"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 safety is covered. The description adds the one thing the annotations cannot: the return behaviour — a single input yields the equivalent in every listed unit. It omits what happens on an unrecognized unit or an out-of-range value.

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?

Two sentences, zero filler, with the quantity scope front-loaded and the input/output contract in the second sentence. Nothing is redundant with the title.

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?

With no output schema, the description correctly states what comes back (all listed units), and it compensates for the missing unit enum. For a simple two-parameter converter that is essentially sufficient; only error/edge-case behaviour for unsupported units is unaddressed.

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

Parameters4/5

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

Schema description coverage is 0% and there is no enum on the unit parameter, so the description carries the burden; by enumerating the accepted strings (cd/m2, kcd/m2, stilb, lambert, ft-L) it supplies the value domain the schema lacks. It does not explain the meaning of 'value' or its numeric bounds, but those are documented in the schema via title/minimum/maximum.

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 names a specific verb and resource (convert luminance) and scopes it to screen/emitting-surface luminance, which separates it from neighbours like bpj_units_illuminance and bpj_color_luminance_grayscale. It stops short of naming an actual sibling as the alternative, so it is clear but not maximally differentiating.

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?

It tells the agent how to call it (enter one of five listed units, get the equivalent in every unit), which implies the conversion use case. There is no explicit when-to-use versus a sibling converter, no exclusions, and no handling guidance for an unsupported unit string.

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.