Hopi

Running pace calculator

hopi_running_pace_calculator

Read-onlyIdempotent

Work out running pace, finish time or distance, in kilometres or miles. Mode 'pace' needs distance and timeSeconds; mode 'time' needs distance and paceSeconds (seconds per unit); mode 'distance' needs timeSeconds and paceSeconds. Distance is in the chosen unit. Returns pace per km and per mile, speed in km/h and mph, distance and total time. Source: https://hopi.co.uk/running-pace-calculator/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes	Which value to solve for
`unit`	No	Unit for distance and the given pace. Default 'km'	km
`distance`	No	Distance in the chosen unit (needed for 'pace' and 'time' modes)
`paceSeconds`	No	Pace in seconds per unit (needed for 'time' and 'distance' modes)
`timeSeconds`	No	Total time in seconds (needed for 'pace' and 'distance' modes)

Output Schema

TableJSON Schema

Name	Required	Description
`kph`	Yes
`mph`	Yes
`mode`	Yes
`time`	Yes
`unit`	Yes
`summary`	Yes
`distance`	Yes
`pacePerKm`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`pacePerMile`	Yes
`timeSeconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedOutput schema / required

Added value: +[
+  "distance",
+  "kph",
+  "mode",
+  "mph",
+  "pacePerKm",
+  "pacePerMile",
+  "source_url",
+  "summary",
+  "time",
+  "timeSeconds",
+  "unit"
+]

First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this read-only and non-destructive. The description adds useful behavioral detail by specifying the output set: 'pace per km and per mile, speed in km/h and mph, distance and total time.' It also clarifies that distance is interpreted in the chosen unit. No contradiction with annotations.

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 compact and front-loaded: it states the core purpose first, then mode-specific requirements, then outputs. The source URL adds minor extra noise, but the overall structure is efficient and easy to scan.

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 rich schema with conditional requirements, the full coverage of parameter descriptions, the safety annotations, and an output schema, the description is complete enough for an agent to select and invoke the tool correctly. The description also states the modes, required inputs, and returned values explicitly.

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 coverage is 100%, with property descriptions and conditional required fields already documenting each parameter. The description restates the mode-parameter relationships and the seconds-per-unit meaning, which is helpful but largely redundant with the schema's structured information.

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 opens with a specific verb and resource: 'Work out running pace, finish time or distance, in kilometres or miles.' It names the three distinct calculation modes ('pace', 'time', 'distance'), making the tool's function immediately clear and distinguishable from the many other calculator siblings.

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?

The description gives clear, mode-specific usage guidance by stating exactly which parameters each mode requires. It does not explicitly mention alternative tools or when not to use this one, but the mode conditions leave little ambiguity about how to drive the tool correctly.

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

All Hopi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?