Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

math_running_pace_converter

Read-onlyIdempotent

Convert running pace and speed between min/km, min/mi, km/h, mph. Compute race splits for 5K, 10K, half, marathon. Predict finish times using the Riegel formula.

Instructions

Running Pace and Speed Converter. Convert running pace and speed, compute race split times, or predict a race time with Pete Riegel 1981 formula, selected by the operation field. convert converts one value between min/km, min/mi, km/h, and mph (pace is decimal minutes on the wire, e.g. 5.5 means 5 minutes 30 seconds). splits projects 5K, 10K, half-marathon (21.0975 km), and marathon (42.195 km) finish times from a sustained pace. predict scales a known race time to a target distance via the Riegel power law. Use math_unit_converter instead for general length/volume conversion and math_fuel_consumption_calculator for fuel economy. Pure local arithmetic: read-only, non-destructive, deterministic, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Invalid input returns HTTP 400 with an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoMode selector. convert needs value, fromUnit, toUnit. splits needs pace, paceUnit. predict needs knownDistance, knownTime, targetDistance (exponent optional). Defaults to convert when omitted.convert
valueNoconvert: the figure to convert. Must be greater than 0. A pace value is decimal minutes (5.5 is 5 minutes 30 seconds); a speed value is in the fromUnit.
fromUnitNoconvert: unit of value. Pace units are min_per_km and min_per_mi; speed units are km_per_h and mph.
toUnitNoconvert: unit to convert value into.
paceNosplits: sustained pace as decimal minutes per unit (5.5 is 5 minutes 30 seconds). Must be greater than 0.
paceUnitNosplits: unit the pace is expressed in.
knownDistanceNopredict: a distance alias (km, mi, 5K, 10K, half_marathon, marathon) or an object with a positive km number.
knownTimeNopredict: the achieved time as HH:MM:SS or MM:SS (a number of seconds is also accepted). Must be greater than 0.
targetDistanceNopredict: distance to predict, same accepted forms as knownDistance.
exponentNopredict: Riegel fatigue exponent in the range above 0 up to 2. Defaults to 1.06.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoEcho of the operation that ran (convert when omitted).
dataNoOperation-specific result. convert returns fromUnit, toUnit, fromValue, toValue (numbers) plus formattedFrom, formattedTo (strings). splits returns pace, paceUnit plus a splits object keyed 5K/10K/half_marathon/marathon, each with time (string) and seconds (number). predict returns knownDistance, targetDistance (echo), knownTime, predictedTime (strings), predictedSeconds, exponent (numbers).
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds rate limiting (60 req/min anonymous), deterministic and local nature, and error behavior (HTTP 400). No contradictions.

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?

Concise 6 sentences covering all aspects without redundancy, front-loaded with purpose, well-organized.

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 complex tool with multiple operation modes and 10 parameters, the description adequately covers purpose, usage, behavior, and error handling. Output schema covers return values.

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

Parameters3/5

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

Schema already describes all parameters (100% coverage). Description adds minimal beyond explaining decimal minutes format and operation-specific roles, but not enough to warrant a higher score.

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 running pace/speed, computes splits, and predicts race times via operation field. It explicitly distinguishes from siblings by directing general conversions to math_unit_converter and fuel economy to math_fuel_consumption_calculator.

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?

Description provides explicit when-to-use for each operation (convert, splits, predict) and when-not-to-use by naming alternative tools for general conversions and fuel economy.

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