Skip to main content
Glama

Illuminance unit converter

bpj_units_illuminance
Read-onlyIdempotent

Convert incident light on work surfaces. Enter one of lx, klx, fc, phot 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_illuminance"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing the return shape: the equivalent value in every listed unit. It does not describe rounding, precision, or output ordering, which are the remaining behavioral unknowns for a converter.

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?

Two tight sentences with the purpose front-loaded and the input/return contract immediately after. Minor awkwardness in "convert incident light" (values are converted, not light) but no wasted words.

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?

For a two-parameter, annotation-rich converter with no output schema, the description covers purpose, accepted units, and the multi-unit return, which is what an agent needs to call it correctly. Missing only secondary details such as output precision and unit-token case handling.

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?

Schema description coverage is 0%, so the description must carry the parameter burden; it partially does by enumerating the four accepted unit tokens and identifying the value as the input quantity. It does not clarify case sensitivity, whether units outside the list are rejected, or how the 0-to-1e12 value bound behaves, so meaningful gaps remain.

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?

"Convert incident light on work surfaces" states a specific verb and a physically specific quantity (illuminance), and naming the units lx/klx/fc/phot makes the resource concrete. It does not explicitly distinguish itself from the sibling bpj_units_luminance, which an agent could easily confuse with illuminance, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Enter one of lx, klx, fc, phot" gives clear input instructions, implying this is the tool for converting among those four units. There is no explicit when-to-use versus the luminance sibling and no statement of exclusions or edge cases (e.g. negative or zero values), so guidance is implied rather than stated.

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.