Skip to main content
Glama

Temperature unit converter

bpj_units_temperature
Read-onlyIdempotent

Convert Celsius, Fahrenheit, Kelvin, and Rankine readings. Enter one of K, degC, degF, degR 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_temperature"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety burden is off the description. The description does add one useful behavioral fact — it returns the value in every listed unit rather than a single conversion — but says nothing about precision, rounding, or handling of values below absolute zero.

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 tight sentences: the first names the domain, the second gives the input contract and the output shape. Nothing is redundant and the essential information is front-loaded.

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?

With no output schema, the description must cover the return, and it does so at a high level ('equivalent value in every listed unit'). For a simple two-parameter converter that is close to adequate, but output structure and precision/edge-case behavior remain unspecified.

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 genuinely earns credit by naming the exact accepted tokens (K, degC, degF, degR). It adds no detail on the value parameter's numeric bounds, which the schema already carries via min/max.

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 ('Convert ... temperature readings') and enumerates the four supported scales, so an agent can immediately tell this is the temperature-specific converter among the unit-conversion family. Differentiation from the closer siblings (temperature_gap, eng_mix_temperature) is not addressed, which keeps it below 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?

The second sentence implies the calling pattern (supply one unit token and a value, receive all equivalents), which is enough to use the tool, but there is no explicit when-to-use/when-not-to-use guidance and no mention of the temperature-gap or mixed-temperature alternatives.

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.