Skip to main content
Glama
Luissalet

Laplace's Hoard MCP Server

by Luissalet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

units_convert

Read-onlyIdempotent

Convert physical quantities between units, including compound inputs, temperature offsets, and derived units, with results rounded to 12 significant digits and a citable reference.

Instructions

Convert a physical quantity to another unit, e.g. quantity="3.5 km/h", to="m/s".

Handles compound inputs ("5 ft 11 in" to "cm"), temperatures with their offsets ("100 degF" to "degC" is 37.78, not a plain scale), and derived units (kWh, psi, mph, g/cm**3). Unit names are English/SI symbols (m, km, mi, ft, in, kg, lb, g, L, gal, degC, degF, K, s, min, h, km/h, mph, J, kWh, W, Pa, bar, psi) or their common Spanish names (metros, kilómetros, millas, pies, pulgadas, libras, kilogramos, litros, horas, minutos...). A decimal comma with no dot in the input ("3,5 km") is read as 3.5, not 35. No currencies (rates need the network). Returns {id, cite, to_magnitude, to_unit, formatted} rounded to 12 significant digits. Cite as its cite, e.g. [L-000042].

Keywords: convert, how many, in meters, in kilograms, miles to km, pounds to kilos, temperature, fahrenheit, celsius, convertir, cuántos, pasar a, en metros, en kilos, millas a kilómetros, libras a kilos, temperatura, grados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
quantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds substantial behavioral detail: compound input parsing, temperature offset handling, decimal comma interpretation, supported unit families, return shape, 12-significant-digit rounding, and citation instructions. This goes well beyond the structured annotations.

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 dense but every sentence contributes: core purpose, examples, edge cases, accepted units, return format, and retrieval keywords. It is front-loaded with the essential conversion behavior and avoids unnecessary filler.

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?

Despite having no output schema, the description discloses the return object fields and rounding behavior. It covers input formats, unit variations, special cases like temperature offsets, and explicit non-support for currencies. An agent has enough to select and invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the full burden. It thoroughly explains both parameters through examples: quantity accepts values like '3.5 km/h' or '5 ft 11 in', and to accepts targets like 'm/s', 'cm', or 'degC'. Supported unit lists and formatting rules add meaning far beyond the bare 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?

States a specific verb and resource: 'Convert a physical quantity to another unit', with a concrete example. The scope is clearly distinct from sibling tools like calc or math, and the keyword list reinforces the conversion purpose.

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?

Provides clear context for when to use the tool: physical unit conversions, compound inputs, temperatures, derived units, Spanish unit names, and decimal comma handling. It also gives an explicit exclusion ('No currencies'), but does not name alternative sibling tools directly.

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