Skip to main content
Glama

temperature_convert

Read-onlyIdempotent

Convert temperature values between Celsius, Fahrenheit, Kelvin, and Rankine for calculations, comparisons, and data normalization.

Instructions

Convert temperature between Celsius, Fahrenheit, Kelvin, and Rankine.

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

Input Schema

NameRequiredDescriptionDefault
fromNoSource unit: c, f, k, or r (default c).
valueYesTemperature value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is fully covered structurally, and the description contributes nothing further. It says nothing about precision/rounding, how offsets are handled, or — most importantly — that only a source unit is supplied, so results presumably come back for multiple target scales.

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?

A single front-loaded sentence with no filler, so it is efficient. It is arguably too terse for a tool whose output set is ambiguous, but nothing is wasted.

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?

The tool is simple, fully annotated, and has complete parameter coverage with no output schema, so the description need not explain return values. Still, the absence of any note on what gets returned given a single 'from' unit and on precision leaves a genuine hole for an agent that must report a number.

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 100% and the 'from' parameter already documents the c/f/k/r codes and its default, so the description's unit list is largely redundant. Because the schema exposes only a source unit and no target, the description's phrase 'between Celsius, Fahrenheit, Kelvin, and Rankine' leaves the agent guessing which outputs it receives; baseline 3 with that caveat.

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?

Specific verb (Convert) plus resource (temperature) with the four supported scales enumerated, which cleanly separates it from convert_length, convert_volume, convert_speed and the other unit converters in the sibling list. It does not, however, distinguish itself from the sibling actually named convert_temperature, which appears to do the same job.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to pick this tool over convert_temperature, nor any prerequisites, input-range guidance (e.g. absolute zero), or note about which direction conversions run. The agent is left to infer everything about selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools