Skip to main content
Glama

Temperature interval unit converter

bpj_units_temperature_gap
Read-onlyIdempotent

Convert temperature differences and changes. Enter one of deltaK, deltaC, deltaF, deltaR 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_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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, non-destructive behavior, so safety needs no restating. The description does add one piece of behavior beyond the annotations: the call returns the equivalent value in every listed unit, not just a single target. It says nothing about error handling for unrecognized units or how a 'delta' input is formatted.

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 short sentences with no waste; the purpose comes first and the input/output contract follows. Every clause earns its place.

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 only two parameters, no output schema, and full annotation coverage, the description supplies what is needed: valid unit tokens and the multi-unit return shape. The remaining gap is the absence of an explicit exclusion for absolute temperature conversion, the most likely sibling confusion.

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%, so the description carries the burden for the non-obvious parameter. It enumerates the four accepted unit tokens (deltaK, deltaC, deltaF, deltaR), which is the key semantic an agent needs. It leaves the numeric 'value' parameter and its magnitude limits to the schema's type bounds.

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 differences and changes') and scopes it to intervals rather than absolute temperatures, which implicitly separates it from the absolute-temperature sibling. It stops short of naming that alternative, so an agent must infer the boundary from the 'delta' unit prefixes.

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 only implied: the agent is told to enter one of the delta units, which signals this is for intervals. There is no explicit when-to-use or when-not-to-use statement, and no warning that absolute temperature conversion belongs to a different tool.

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.