Skip to main content
Glama
s3eidat

S3eidat Tools MCP

by s3eidat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Unit converter

calc_unit_convert
Read-onlyIdempotent

Convert values between units in 14 categories, including length, mass, temperature, data, fuel economy, and cooking, by supplying a value and units or a query like '5 km to mi'.

Instructions

Convert between units in 14 categories, the same table as the website: length, mass, temperature, volume, area (incl. dunam), speed, time, data (kB/MB vs KiB/MiB, bits), pressure, energy, power, angle, fuel economy (L/100km, km/L, mpg US/UK) and cooking (tsp, tbsp, cups, metric spoons). Give value + from + to (symbols like "km", "°F", "GiB" or names like "miles"; ASCII forms like "m2", "um" work), or a query like "5 km to mi". Set all=true for the value in every unit of the category, or list=true to see every category and unit. Web version: https://s3eidat.github.io/unit-convert/

Input Schema

NameRequiredDescriptionDefault
toNoUnit to convert to (symbol or name). Optional when all=true.
allNoAlso return the value in every unit of the category.
fromNoUnit to convert from (symbol or name).
listNoJust list every category and its units.
queryNoA whole question, e.g. "5 km to mi" or "72 f in c".
valueNoThe number to convert.
categoryNoCategory, to pick the right unit when a symbol exists in two (e.g. "pt" in volume and cooking).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds useful behavioral detail about accepted symbol and ASCII forms, query syntax, and what all=true and list=true return.

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 dense but front-loads the core purpose and packs in useful examples and modes without obvious filler. It could be slightly better structured than a single long paragraph, and the website link is optional rather than essential.

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?

For a seven-parameter, all-optional conversion tool with no output schema, the description covers the categories, input forms, disambiguation, and output modes sufficiently for correct invocation. Nothing critical about how to call the tool is missing.

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?

Although schema coverage is already 100%, the description adds substantial meaning beyond the schema: examples of symbols and names, ASCII forms like "m2" and "um", query strings like "5 km to mi", category disambiguation for symbols such as "pt", and the intended effects of all and list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: converting units across 14 named categories. It is much more specific than the title alone, though it does not explicitly differentiate itself from overlapping siblings such as time_convert, base_convert, or bytes_convert.

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 clearly explains the main invocation modes: value + from + to, a natural-language query, all=true for every unit in a category, and list=true for categories/units. It lacks explicit guidance on when to prefer this tool over related sibling converters.

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