Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Unit conversion: convert between units of length, weight, temperature, volume, speed and more

units_convert
Read-only

Convert between units of length, mass, volume (incl. US cups and gallons), temperature (c, f, k), speed, area, data size (kB vs KiB), time, energy and pressure. Example units: km, mi, lb, kg, floz, ml, mph, kn, acre, gib, kwh, psi. Use when exact conversions matter. Example: value=10, from=km, to=mi. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "<from>",
      "to": "<to>"
    },
    "name": "units_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesUnit to convert to
fromYesUnit to convert from
valueYesThe amount

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false. The description adds genuinely new behavioral context: pricing ($0.01/call, first 25 free, failed calls free), payment paths (x402 USDC or card key), and the explicit note that repeated calls are charged, which explains why the tool is non-idempotent in practice. The main omission is what the response looks like (numeric result? formatted string with units?).

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?

Front-loaded with capability scope, then usage hint, example, and cost model, in a logical order with no filler. The pricing/payment detail takes up a fair share of the text, but it is decision-relevant rather than padding.

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?

For a broad multi-domain converter with no output schema and no enum constraints, the definition covers scope, unit format, example invocation, side-effect profile, and cost model. Only the return value shape and behavior on invalid or unknown units are left unstated.

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% but the three fields are terse ('Unit to convert from/to', 'The amount') with zero enums, so the description must define the acceptable unit string format. It does so with a long list of concrete tokens (km, mi, lb, kg, floz, ml, mph, kn, acre, gib, kwh, psi) plus a full example call, which meaningfully exceeds the schema's documentation.

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 and resource ('Convert between units') and then enumerates the covered domains (length, mass, volume, temperature, speed, area, data size, time, energy, pressure) with example units for each family. This level of detail lets an agent distinguish it from neighboring utilities such as geo_distance or calc_bmi without inspecting 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 Guidelines4/5

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

'Use when exact conversions matter' gives a positive selection criterion, and the worked example (value=10, from=km, to=mi) shows the calling shape. There is no explicit when-not guidance or named alternative, so the routing signal is clear but not exhaustive.

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.