Skip to main content
Glama

convert_units

Read-only

Convert exact values between units, including compound units, SI and binary prefixes, temperatures, and currencies, with optional rate dates, rounding, and temperature differences.

Instructions

Exact unit conversion: compound units (km/h, J/(kg*K), L/100km<->mi/gal), SI/binary prefixes, temperatures (degC/degF/K; difference for intervals), currencies (ECB, 3-letter codes). No to = SI base.

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": {
      "from": "<from>"
    },
    "name": "convert_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
dateNocurrency rate date
fromYes
valueNodefault 1; expression ok
digitsNo
differenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description usefully adds behavioral depth: conversion is exact, currency rates come from ECB, 'difference for intervals' explains temperature-delta semantics, and the 'No to' rule defines default resolution. It still does not disclose output shape, rounding behavior tied to digits, or rate staleness, which keeps it below a 5.

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 packed with concrete examples and no filler; every clause carries information. The telegraphic fragments ('No to = SI base', 'difference for intervals') are slightly cryptic, which costs one point on readability.

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?

For a 6-parameter, read-only tool with no output schema, the description covers the major behavioral domains but leaves 'digits' undocumented in both description and schema, and never states the return format for a conversion result. Adequate but with visible gaps given the parameter count.

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 coverage is 33%, so the description must carry weight; it does explain the 'to' default (SI base), the interval meaning of difference, and the ECB source behind the date parameter. However, 'digits' is never explained in the description and 'value'/'expression' behavior is only in the schema, so compensation is partial.

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+resource ('Exact unit conversion') and enumerates the concrete domains it covers: compound units with literal examples (km/h, J/(kg*K), L/100km<->mi/gal), SI/binary prefixes, temperatures, and currencies. This makes it clearly distinguishable from siblings like calc, table_convert, time_convert, and finance without needing to open 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?

Provides implied usage context through the enumerated capability domains and the default-behavior note 'No to = SI base', which tells the agent what happens when the target unit is omitted. It gives no explicit when-to-use-except guidance, no exclusions, and does not name an alternative tool for near-adjacent tasks such as time_convert or table_convert.

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