Skip to main content
Glama

Agent Bits

by dev.agentbits

unit_convert

Convert a numeric value between supported length, mass, or temperature units—for example miles to kilometers or Celsius to Fahrenheit—when you need a deterministic unit conversion.

Use when:

  • Convert 10 miles to kilometers

  • What is 25°C in Fahrenheit?

  • Convert a mass value between kilograms and pounds

Do not use when:

  • Convert currencies or fetch exchange rates (use currency_lookup for metadata only)

  • Convert timestamps or timezones (use timestamp_convert / timezone_convert)

  • Convert unsupported unit categories outside length, mass, and temperature

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
to_unitYes
from_unitYes

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure burden. It adds useful context (deterministic conversion, supported categories), but does not state what happens with invalid unit strings, case sensitivity, precision, or error behavior. This is a moderate gap, not a contradiction.

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 well-structured, concise, and front-loaded. The main purpose is stated first, followed by quick examples and clear exclusions. Every sentence earns its place with no redundant content.

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?

The tool is simple but the description still lacks a full list of supported units and any hint about return values or error handling. It covers usage boundaries well, but not enough to fully compensate for the missing schema descriptions and output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not compensate by defining accepted values for from_unit/to_unit. Examples imply orientation (value, from_unit, to_unit) but no list of supported unit strings, abbreviations, or format requirements. This leaves the parameters underspecified.

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 the verb 'Convert' and the resource 'a numeric value between supported length, mass, or temperature units', with concrete examples. It explicitly differentiates from sibling tools by listing excluded conversions (currencies, timestamps, timezones) and suggesting alternatives.

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

Usage Guidelines5/5

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

The description provides 'Use when' and 'Do not use when' sections, giving concrete example queries and explicitly naming alternative tools (currency_lookup, timestamp_convert, timezone_convert). This is exactly the kind of guidance needed for selecting this tool vs siblings.

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

All Agent Bits 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

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct data format and operation, with explicit 'Do not use when' cross-references to prevent confusion. For example, base64_encode/decode, url_encode/decode, and timestamp_convert/timezone_convert are clearly separated, and the various validators (ISBN, Luhn, UUID, JSON) apply to different identifiers.

Naming Consistency4/5

Most tool names follow an object_operation pattern (e.g., base64_decode, country_lookup, timestamp_convert), using lowercase with underscores. The main deviation is countries_bulk, which uses a noun+adjective form without an explicit operation, making it inconsistent with the verb-like operations used elsewhere.

Tool Count3/5

With 18 tools, the server falls into the 16-25 range which feels heavy for a utility collection. While each tool is individually useful and the scope is broad, the count is higher than typical for a well-focused server and may overwhelm agents scanning the available options.

Completeness4/5

The set provides solid coverage of encoding/decoding, validation, lookups, and conversions, with paired encode/decode and convert functions. However, some common utilities such as hashing, HTML entity encoding, UUID generation, or email validation are absent, leaving minor gaps for agents that need those operations.

Resources