MCP serverio.github.joeyaflores/ourpr-courses

Whether one particular run was an interval session, and its reps.

Read one published course: its place, distance, climb, how it was measured, and which streets carry it. DELIBERATELY WITHOUT the elevation profile, the amenities and the centerlin

Public drinking water and toilets on the line of one course, each placed at the mile it sits at. READ THIS LIMIT BEFORE YOU ANSWER. These come from OpenStreetMap: public taps and

Where a course actually runs: its start, its finish, its bounding box, every mile marker, and the streets in the order you meet them. The GPX file is free and needs no account. Ha

The elevation profile of one course, sampled, plus every climb and descent ourpr. named on it. THIS IS THE TOOL FOR "what are the hills and where". Each named section carries the

One activity in full: mile splits with heart rate, cadence, calories, device. Id comes from ourpr_list_runs. For the profile along the route, use ourpr_run_stream.

Read one trail system: how many miles of path it holds, how many ways were mapped, where it sits, and where the measurement came from. Args: - slug (string): From ourpr_list_tra

List every running course published on ourpr., with its place, distance, climb and next race date. Each course is a MEASURED centerline built from recorded runs, with elevation fr

The runner's planned runs between two dates: day, name, miles, time, tag, the runner's note, whether a logged run fulfilled it, and whether ourpr. create wrote it. Read it before o

Every race ourpr. finds in the history, newest first, tune-ups included: date, name, distance, time, pace and run id. Also the fastest result at 5K, 10K, half marathon and marathon

Training history between two dates, newest first: date, local start, name, type, miles, pace, time, elevation, average heart rate, and on a runs-only list Friel's efficiency factor

List every trail system ourpr. maps. A trail system is a whole network of connected paths, measured end to end, not a single route through it. Args: - response_format ('markdown

Write one planned run, or a week of them, onto days still ahead. Each lands on the runner's week as a plan they can see, edit and remove. Needs a token made with the write scope an

Interval sessions found across the history, with reps and distances. Detection is conservative, so a session it misses is still in ourpr_list_runs.

The laps the watch recorded for one run — the runner's own button presses. Laps follow the workout; mile splits follow the mile.

A run's profile on a 10 m grid — elevation, heart rate, power, cadence — as min, average, max and coverage per channel, not every sample. Also each half by distance with its moving

Stretches of past runs matching a distance and climb — what the runner has already done that resembles a race they are training for.

The goal race and its Block: race day, distance, goal time, which week of the Block today falls in, and miles for each week. Also the Blocks before past races, each with its result