Skip to main content
Glama

curatedapi

Temperature converter

calc_units_temperature
Read-only

Convert temperatures between Celsius, Fahrenheit, kelvin and Rankine.

Converts a temperature reading, or a temperature difference, between scales. A reading uses the scale offsets (0 °C = 32 °F); a difference does not (a rise of 10 °C is a rise of 18 °F). All factors are exact.

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>",
      "from_unit": "<from_unit>"
    },
    "name": "calc_units_temperature"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesThe temperature (or temperature difference) to convert.
optionsNoPrecision and rounding of the results (default: rounding=half_even, significant_digits=15).
to_unitNoScale to convert to. Omit to convert to every scale. Options: C: degree Celsius; K: kelvin; F: degree Fahrenheit; R: degree Rankine
quantityNoWhether the value is a reading or a difference between two readings. Options: reading: a temperature reading, like 20 °C; difference: a change or interval, like a rise of 5 °Creading
from_unitYesScale of the value. Options: C: degree Celsius; K: kelvin; F: degree Fahrenheit; R: degree Rankine

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish this as a safe, read-only, closed-world operation, so the description's job is lighter. It adds genuine behavioral context by explaining that readings use scale offsets (0 °C = 32 °F) while differences use pure factors, and that all factors are exact — important for interpreting results, though it says nothing about output shape or the 'omit to_unit converts to all scales' behavior.

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?

Three short sentences, front-loaded with the core purpose followed by the one non-obvious semantic distinction. There is minor redundancy between 'Convert temperatures between...' and 'Converts a temperature reading... between scales', but no sentence is wasted.

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?

With an output schema present, annotations covering safety, and 100% schema description coverage, the description only needs to cover the tricky conceptual area — and it does, fully explaining the reading/difference distinction that drives correctness of calls.

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 coverage is 100%, so the baseline is 3, but the description adds conceptual meaning beyond the enum labels by explaining why 'difference' skips the offsets ('a rise of 10 °C is a rise of 18 °F'). That clarification helps an agent choose the correct value for quantity, though the options/precision parameters are left entirely to the schema.

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?

The description names a specific verb and resource ('Convert temperatures between Celsius, Fahrenheit, kelvin and Rankine') and enumerates the exact scales covered, so an agent can immediately distinguish it from sibling unit converters like calc_units_length or calc_units_mass.

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?

Usage is implied by the obvious conversion framing, and the reading-vs-difference discussion hints at when each mode applies. However, there is no explicit when-to-use/when-not-to-use guidance or named alternative, so an agent must infer the routing.

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.

Resources