Skip to main content
Glama

utility-converter

by io.github.punchfan01

convert_units

Convert a value between units of length, weight, or temperature.

Supported units:

  • Length: mm, cm, m, km, inch, ft, yard, mile

  • Weight: mg, g, kg, ton, oz, lb

  • Temperature: C, F, K (Celsius, Fahrenheit, Kelvin)

Both units must belong to the same category (e.g. km -> mile is valid, kg -> mile is not).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesThe numeric value to convert.
to_unitYesThe target unit (e.g. "mile").
from_unitYesThe source unit (e.g. "km").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, but the description discloses the key behavior: conversion is only valid within the same category. It also lists all supported units, making the tool's capabilities transparent.

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?

The description is concise: one sentence for purpose, a list of units, and a constraint. It is well-structured and front-loaded with the main action.

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?

Given that an output schema exists (though not shown), the description does not need to explain return values. It covers all necessary context: supported units, categories, and constraints.

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?

The input schema has 100% description coverage, but the description adds a list of supported units and the category constraint, which provides context beyond the schema.

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?

The description clearly states it converts values between units of length, weight, or temperature. It distinguishes from sibling tools like calculate, calculate_date, and get_exchange_rate by specifying the domain of unit conversion.

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?

It provides clear guidelines: both units must belong to the same category (e.g., length to length). While it doesn't explicitly state when not to use it, the list of supported units and categories gives enough context for appropriate use.

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

All utility-converter toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation5/5

All seven tools have clearly distinct purposes: arithmetic, date operations, timestamp conversion, unit conversion, Base64 encoding, currency exchange, and hashing. No two tools overlap in functionality, making disambiguation straightforward.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., convert_units, calculate_date). The names are descriptive and predictable, with the only exception being 'calculate' which is a single verb but still fits the pattern.

Tool Count5/5

With 7 tools, the server is well-scoped for a utility converter. Each tool addresses a distinct need (math, dates, timestamps, units, encoding, exchange rates, hashing) without unnecessary redundancy or excessive complexity.

Completeness4/5

The tool set covers common utility conversions and calculations, including arithmetic, dates, units, timestamps, encoding, exchange rates, and hashing. Minor gaps exist (e.g., no string or color conversion), but the core workflows are well-supported and functional.

Resources