Tredict

Returns detailed metrics and time series for a single executed activity. Examples metrics: " positionLat, positionLong, speed, distance, altitude, cadence, power, heartrate, respirationRate, vo2max, temperature (measured by the watch - this could be at the wrist), weather, runningEffectiveness, effort, intensityDistribution, zonesDistribution, powerAerobicFactor, speedIndex, formPowerFactor, equipment ". By default only the standard time series are returned. Further series, like running dynamics or cycling pedal metrics, are available with the 'allSeries' parameter. The laps of the activity can additionally be included with the 'withLaps' parameter.

activity

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.

add-plan-training

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

zones-distribution

List of body values and health data represented by revisions over time. 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. Possible metrics are: "restingHeartrate" "hrRestDynamic" "hrMaxDynamic" "bodyHeightInCentimeter" "weightInKilograms" "bodyFatInPercent" "bodyWaterInPercent" "muscleMassInPercent" Annotations: restingHeartrate: The resting heart rate, also known as the static resting heart rate, is the heart rate one can repeatedly achieve when one is completely relaxed. The static resting heart rate is used to calculate exertion levels using heart rate, VO2 max and other capacity indicators. hrRestDynamic: Your dynamic resting heart rate is the lowest heart rate one have reached during the day and is usually measured by a fitness watch. One's dynamic resting heart rate is affected by factors such as stress or illness and may therefore not reflect one's true capacity.

bodyvalues

List of capacity values represented by revisions over time for each sportType. 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. Possible metrics are: "hrMax" "hrLth" "ftp" "ftpa" Annotations: hrMax: Maximum heart rate hrLth: Lactate threshold heart rate ftp: Functional Threshold Power ftpa: Functional Threshold Pace

capacity

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.

plan-creation

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

planned-workout

List of Heart Rate Variability data of the user. Each date tag is in the format of "YYYYMMDD" It should traversed in date back to the past and to older entries. A date tag contains a tuple, where the first entry is the calculated HRV value, specifiaclly the "RMSSD during the night", the second entry is the basline over a course of 2 weeks. If the first tuple entry, the RMSSD, diverts significantly from the basline it is too high or too low.

hrv-list

List of all user equipment including bikes, shoes, swimming gear and miscellaneous items. Each equipment entry contains: - "id": Unique equipment identifier - "type": One of "bikes", "shoes", "swimming", "misc" - "name": Name of the equipment - "usageRange": Object with "start" and "end" dates defining the active usage period. "end" is null if still in use. - "count": Number of activities using this equipment - "duration": Total duration in seconds across all assigned activities - "distance": Total distance in meters across all assigned activities Depending on the type, additional fields may be present: - Shoes: "size", "weight" (grams), "drop" (mm) - Bikes: "weight" (grams) - Swimming/Misc: "itemtype", "size", "weight" (grams) - All types: "notes", "previousDistance" (distance before tracking in meters)

equipment-list

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 pace 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.

activity-list