calculate_running_pace
Use this when you know a distance and the time it took (or a target time) and need the pace, the equivalent speed, or the time that pace gives over standard race distances. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do...
This record as markdown: /tools/com-tttkmbb-calcgrid/calculate-running-pace.md
What calculate_running_pace does on Calcgrid
AI agents call calculate_running_pace to retrieve information from Calcgrid without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
time | string | Yes | Elapsed time as h:mm:ss (1:45:00), mm:ss (50:00) or plain minutes (50). |
distance | number | Yes | Distance covered, in the unit given by distance_unit. |
distance_unit | string | — | Unit of the distance input. |
Parameters from the server's own tool schema.
Why calculate_running_pace is rated Low
Even though calculate_running_pace only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs calculate_running_pace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Calcgrid, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calculate_running_pace, this is the rule to start with:
calculate_running_pace is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Calcgrid, apply this rule, and every calculate_running_pace call is checked against it from then on.
Questions about calculate_running_pace
Use this when you know a distance and the time it took (or a target time) and need the pace, the equivalent speed, or the time that pace gives over standard race distances. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you want a realistic prediction of a longer race from a shorter one (pace slows with distance; use race-time-predictor), or you only need to convert between pace and speed units (use pace-converter). What it computes: Computes running pace in min/km and min/mile and speed in km/h and mph from a distance and elapsed time, and projects the finish time for 5 km, 10 km, half marathon and marathon at that constant pace. Inputs: distance (number); distance_unit (enum, optional); time (string). Complete JSON argument examples: {"distance":10,"distance_unit":"km","time":"50:00"} | {"distance":5,"distance_unit":"mi","time":"45:00"} Outputs: pace_min_per_km [min:sec/km], pace_min_per_mile [min:sec/mi], pace_seconds_per_km [s/km], speed_kmh [km/h], speed_mph [mph], distance_km [km], time_5k [h:mm:ss], time_10k [h:mm:ss], time_half_marathon [h:mm:ss], time_marathon [h:mm:ss]. Formula: pace_s_per_km = time_seconds / distance_km; pace_s_per_mile = pace_s_per_km × 1.609344; speed_kmh = 3600 / pace_s_per_km; speed_mph = speed_kmh / 1.609344; time(D) = pace_s_per_km × D for D = 5, 10, 21.0975, 42.195 km Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/running-pace with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/fitness/running-pace.md. It is categorised as a Read tool in the Calcgrid MCP Server, which means it retrieves data without modifying state.
calculate_running_pace accepts 3 parameters: time, distance, distance_unit. Required: time, distance. The full parameter table on this page comes from the server's own tool schema.
Register the Calcgrid MCP server in PolicyLayer and add a rule for calculate_running_pace: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Calcgrid. Nothing to install.
calculate_running_pace is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the calculate_running_pace rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for calculate_running_pace. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
calculate_running_pace is provided by the Calcgrid MCP server (https://tttkmbb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Calcgrid, and thousands of servers like it.
This server
Across the catalogue