Tredict

Returns detailed metrics and time series for a single executed activity.

Examples metrics: " positionLat, positionLong, speed, distance, altitude, cadence, power,

weather, runningEffectiveness, effort, intensityDistribution, zonesDistribution, powerAerobicFactor, speedIndex, formPowerFactor ".

List of already executed activities with activity summaries. If the 'pageSize' limit is reached in the result, there will be a 'nextCursor' in the pagination object. Call the next page with the nextCursor as startDate. Each 'activitList' entry contains at least the activity 'id', 'date' and 'sportType'. If you need extended summaries on all entries in this list call this tool "activity-list" with the "extendedSummary" parameter set to "1". The extended summary contains trainingType, pace, speed, heartrate, temperature, power, cadence, calories, distance, altitude, durations. Be careful as this can lead to significantly larger datasets, if there are lot of results, f.ex. when querying over multiple years. If you need an extended summary with title, notes and metrics only for a single activity, or if you need time series, like the heart rate series, call the "activity" tool with the appropriate 'id' retrieved from this list. If the tool only returs instructions, without any training session and without erroring, then there are simply no training sessions for this date range.

Update fields like 'title' or the 'notes' on an single activity or planned/scheduled workout.

Always ask the user, the human-in-the-loop, for confirmation, if you would like to call this tool. Do not batch call this tool. Ask for confirmation on each activity.

Never apply title or notes updates on your own.

The 'title' is the activity title with a maximum length of 255 characters. If you want to remove the title of an activity pass an empty string "", then Tredict will apply it's default. Do not set this param at all, if you do not want to change the title.

The 'notes' field is a longer description or notes of the activity with maximum length od 2048 chars. It can keep interesting details of an workout or activity.

If reseting a field with an empty string should not be enough, you can search for an object named 'mcpUpdatedFields' in an activity either with the 'activity' tool for executed activities or in the list of planned activities with the 'planned-workout-list' tool. The 'mcpUpdatedFields' object contains older titles and notes with a datestring, when they were backuped.

Add a single planned training (structured workout) to a plan you created with the 'plan-creation' tool before. Use this tool to add the planned trainings by single tool call for each training to the training plan that should be build for the user.

Call this to create a reusable training plan in the ‘My Own Training Plans’ category of Tredict (this is not the actual training calendar). Later on, the plan can be applied by the Tredict user to a custom start or end date in the user's training calendar, either by the user themselves or even in the calendars of athletes associated with the user. If the user has connected an appropriate sports watch manufacturer in Tredict, the plan, when applied, including the structured workouts and planned trainings, will be automatically transferred to the sports watch. Prefer to add the activities to the new plan step by step with the 'add-plan-training' tool. After plan creation, another tool called ‘show-plan-ui’ can be called with the planId to open the MCP app user interface for that plan, which gives a great user experience.

Returns the details and structure of a planned structured workout in JSON.

List of planned and scheduled trainings or structured workouts.

Each 'plannedWorkoutList' entry contains these fields: Fieldname, optional, description id = The unique id of the training session. Alias: workoutId date = Scheduled date of the training session. updatedAt = Last time the user updated the training session. You can compare on this date for updates. timezone = Timezone in hours. '2' means GTM+2. sportType = The sportType can be 'running', 'cycling', 'swimming', 'misc'. title = (Optional) If the user manually defined a title this is given here. notes = (Optional) If the user manually defined a description or notes this is given here. distance = (Optional) The summed up distance in meters of the planned workout segments. duration = (Optional) The summed up duration in seconds of the planned workout segments. Do not calculate a pace from distance and duration. There could be segments with neither both. executedTrainingId = (Optional) Set with the 'activityId' of an executed activity (training), if this planned workout session has a executed activity attached. You can call the "activity"-tool to get detailed information on the executed activity for comparision with this planned workout.

Shows standard metrics, timeseries, laps and a map of an executed activity by activityId.

Shows a reusable training plan created in the users 'My Plans' category by planId.

List of zones represented by revisions over time for each sportType and then the "zoneType".

"zoneType" can be of "heartrate", "pace", "power" or "cadence". A single zone row has an "intensity" field attached, values are mapped like this: 0 = low intensity, 1 = medium intensity, 2 = high intensity Also a single zone row has "from" and "to" fields to define the zone range.

Each list entry represents a so called revision defined by the "timestamp", which only includes changed/updated values/metrics in relation to the last presence of the related metric in an older revision.

The last occurence of a specfic metric as the neighbour to an f.ex. an activity related to the older timestamp of a revision is the valid one.

List of aggregated zones distributions calculated by the time series data points activities have.

The distribution are sorted by sportType and the monthly YYYYMM date tag. Each date tag has training intensity zone distributions based on metrics like pace, power, cadence or heart rate recorded during workouts.

Therein are objects with the zone revision date as key. This revison date in combination with sportType and zoneType can be used to fetch the zone definitions with help of the 'zones' tool.

If there is no revision date, but instead "template", this means the user never defined it's zones revisions, yet, and it's base on the Tredict own zones template. Feel free to ignore then.

A specific distribution contains an array which has to be mapped to the defined zones revision. Each zone row contains another array with 3 entries representing the time spent in the intensityType of 0=low,1=medium,2=high.

Hint: Reducing the zone rows results in the "Intensity Distribution" instead.

Key abbrevations in the zones object are: c = Cadence p = Power pa = Pace h = Heart rate