Skip to main content
Glama
aiexp1

Tanod MCP server

utilpeek: convert units of measurement (exact factors)

convert_units
Read-onlyIdempotent

Convert a numeric value from one measurement unit to another in the same category, such as length, mass, temperature, volume, pressure, energy, power, data size, time, or fuel economy.

Instructions

utilpeek: Convert units of measurement: length, weight, temperature, volume, pressure, energy, data size. For numbers in words use text_numbers. Returns a value converted between two units of one category, with the exact factor: length, mass, temperature (with offsets), volume (US and imperial), area, speed, pressure, energy, power, data size (kB = 1000 bytes, KiB = 1024), time and fuel economy (reciprocal). Cross-category or unknown units, ambiguous spellings (KB), temperatures below absolute zero and 0 into a reciprocal fuel unit are a 422 before any payment (not charged). gal, qt, pt, cup and fl_oz are US; the imperial ones end in _imp. Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/unit-conversion-api.html

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesUnit to convert to, of the same category as `from`.
fromYesUnit to convert from: a symbol or name such as in, ft, mi, kg, lb, C, F, K, L, gal, gal_imp, m2, acre, km/h, mph, kn, psi, inHg, atm, kWh, BTU, eV, hp, kB, KiB, Mbit, h, L/100km, mpg, mpg_imp. Case matters only where it must (kB vs kb, MB vs Mb).
valueYesThe number to convert (at most 1e300 in magnitude).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
kindNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
valueNo
factorNo
offsetNo
resultNo
formulaNo
to_nameNo
categoryNo
from_nameNo
factor_exactNo
offset_exactNo
factor_decimalNo
offset_decimalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds substantial extra context: exact-factor returns, 422 error conditions before payment, no-charge guarantee, US vs imperial unit conventions, typical latency, price, free tier, and documentation link.

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?

The description is front-loaded with the core purpose and stays in one dense paragraph. It has minor redundancy: the category list appears twice with slight variation ('weight' vs 'mass'), and the 'utilpeek:' prefix repeats the title.

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?

An output schema exists, so return-value structure need not be explained. The description is thorough for a conversion tool, covering scope, supported categories, error cases, payment/free-tier behavior, latency, and external docs.

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 100%, so the baseline is 3. The description adds meaningful unit-category semantics beyond the schema, including US vs imperial suffixes, exact data-size conventions (kB vs KiB), reciprocal fuel units, and ambiguous-spelling handling.

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 ('Convert') and resource ('units of measurement') and enumerates the supported categories. It also names the sibling text_numbers as the right tool for numbers written in words, so an agent can distinguish it from at least one alternative.

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

Usage Guidelines4/5

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

Gives clear usage context (units of measurement) and an explicit alternative for numbers in words ('use text_numbers'). It does not, however, distinguish this tool from the sibling convert_time, even though it claims to handle time and fuel economy.

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