Skip to main content
Glama

Power unit converter

bpj_units_power
Read-onlyIdempotent

Convert appliance and mechanical power ratings. Enter one of W, kW, mW, MW, hp_mech, PS, Btu_IT/h 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_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context by saying the result is returned in every listed unit and by scoping the tool to appliance and mechanical power ratings; it does not discuss rounding or precision.

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 tightly written sentences with the core action and accepted units front-loaded. There is no redundant wording, and the output behavior is stated efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter conversion tool with rich annotations and no output schema, the description supplies the essential input vocabulary and explains that output contains all listed units. Nothing important for correct invocation appears to be missing.

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?

With schema description coverage at 0%, the description compensates by spelling out the accepted unit tokens, which the schema only weakly signals in a title and does not enforce with an enum. It still does not explain value bounds or unit case sensitivity, but the critical unit vocabulary is covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — converting power ratings — and enumerates the exact unit set, which distinguishes it from the many other bpj_units_* converters. An agent can identify this as the power converter without opening the schema.

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?

The unit list implies when to use the tool, but there is no explicit guidance on when to prefer or avoid it versus related converters such as energy or force. It provides context but no exclusions or alternative-routing instructions.

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.