Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

math_unit_converter

Read-onlyIdempotent

Convert numeric values between units within physical quantity categories using exact NIST conversion factors. Supports length, mass, volume, area, energy, power, pressure, temperature, and speed.

Instructions

Physical Unit Converter. Convert a numeric value between two units within a single physical-quantity category, using exact NIST SP 811 conversion factors. Supported categories are length, mass, volume, area, energy, power, pressure, temperature, and speed; the from and to units must both belong to the chosen category. Temperature is handled by formula (Celsius/Fahrenheit/Kelvin/Rankine); all other categories use a to-base multiplicative factor. Use math_running_pace_converter instead for running pace/speed splits and race-time prediction, file_file_size_calculator for digital storage units (KB/KiB/MB/MiB), and math_currency_converter for money at daily FX rates. Three operations: convert (default), listCategories (names of all categories), and listUnits (unit ids/names/symbols for one category). Runs locally on the value you provide: read-only, non-destructive, contacts no external service, deterministic, and rate-limited (60 requests/minute for anonymous callers). The convert result returns the numeric outpu

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoAction to run. convert requires category, fromUnit, toUnit, value. listUnits requires category. listCategories needs no other field.convert
categoryNoPhysical-quantity category. Required for convert and listUnits. Both fromUnit and toUnit must be valid ids within this category.
fromUnitNoSource unit id within category. Required for convert. Examples: length m/cm/km/in/ft/mi; mass kg/g/lb/oz; volume L/mL/gal_us; area m2/acre/ha; energy J/kWh/BTU; power W/kW/hp_metric; pressure Pa/bar/psi; temperature K/C/F/Ra; speed m_s/km_h/mph/knot. Call listUnits to enumerate a category.
toUnitNoTarget unit id within the same category. Required for convert. Same id set as fromUnit; call listUnits to enumerate valid ids for a category.
valueNoNumeric quantity to convert, expressed in fromUnit. Required for convert. Accepts a JSON number or a numeric string (integer, decimal, or scientific notation); must be finite.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe operation that was performed (convert, listCategories, or listUnits).
dataNoOperation payload. For convert: an object with category/fromUnit/toUnit/fromValue/toValue/formattedFrom/formattedTo. For listCategories: an array of category name strings. For listUnits: an array of unit objects with id, name, symbol, and factor or formula.

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds valuable runtime behavior: local execution, no external service contact, deterministic, rate-limited (60 req/min), and exact NIST conversion factors. This goes beyond annotations without contradicting them.

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, front-loading the core purpose, then providing usage guidance, behavioral details, and parameter examples. Every sentence adds value, and there is no redundancy. The truncated ending is assumed complete; otherwise still concise.

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 the tool's moderate complexity (5 parameters, 3 operations, many categories) and the presence of an output schema, the description covers all essential aspects: purpose, supported categories, behavioral traits, usage guidelines, and operation semantics. No significant gaps.

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?

With 100% schema coverage, baseline is 3. The description enhances parameters by listing examples for fromUnit/toUnit (e.g., 'length m/cm/km/in/ft/mi') and explaining the category enumeration. This adds meaningful 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 is a physical unit converter, specifies the exact operation (converting numeric values between units within a category), lists all supported categories, and differentiates from sibling tools like running pace, file size, and currency converters by naming alternatives explicitly.

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?

Provides explicit guidance on when to use this tool versus alternatives (e.g., 'Use math_running_pace_converter instead for running pace/speed splits...'). It also explains the three operations (convert, listCategories, listUnits) and their typical usage contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server