Skip to main content
Glama

Energy unit converter

bpj_units_energy
Read-onlyIdempotent

Convert electrical usage, work, and heat. Enter one of J, kJ, MJ, Wh, kWh, cal_th, kcal_th, Btu_IT 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_energy"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the non-obvious behavioral fact that a single call returns the equivalent in every listed unit rather than in a chosen target unit, which is genuinely useful and not derivable from annotations or 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?

Two sentences, no filler, with the conversion scope front-loaded and the accepted-unit list immediately after. Every clause carries information the agent needs.

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 explains the shape of the response (equivalents in every listed unit), which is the main thing an agent must know before calling. Minor gaps remain: no statement of numeric precision or rounding, and no note that unit casing/spelling must match exactly beyond the parenthetical list.

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 field, so the description is the only place the eight permissible unit tokens (including the exact spellings cal_th, kcal_th, Btu_IT) are enumerated. That is real compensation for the schema gap. It does not explain the non-negative or maximum bound on value, which the schema carries on its own.

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 and resource ("Convert electrical usage, work, and heat") and enumerates the eight accepted units, so the energy domain is unmistakable against siblings like bpj_units_power or bpj_units_torque. It stops short of explicitly naming a sibling or stating how it differs from adjacent quantity converters, so it lands at 4 rather than 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?

It tells the agent how to drive the tool ("Enter one of J, kJ, ...") and what comes back, which implies the single-value, single-unit usage pattern. There is no explicit when-to-use or when-not-to-use guidance, and no mention of checking non-energy quantities against the other bpj_units_* tools.

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.