COROS

Query the user's bound COROS devices. Returns a list of devices including device ID, firmware type, and custom name. Use this when the user asks about their devices, watches, or equipment.

Query the user's COROS fitness assessment overview. Returns VO2max, running level, threshold pace, and race predictions. Use this when the user asks about current fitness assessment, running ability, VO2max, threshold pace, or predicted 5k/10k/half-marathon/marathon results.

Query the user's COROS wellness check time series. Returns raw heart rate, HRV, stress, respiration rate, and SpO2 data from the latest complete wellness check in a specified yyyyMMdd date range, or from the recent-days window when no date range is given. Explicit dates query daily/queryPb dailyRhmList; recent queries also use dailyRhm history. Dates are calculated in the user's COROS timezone. The recent query window is capped at 7 days.

Query the user's COROS menstrual cycle data. Returns today's menstrual status, the next period start date, daily phase status, cycle date ranges, and user notes. If startDay or endDay is not provided, it queries from 30 days before today to 365 days after today. Dates are calculated in the user's COROS timezone. Use this when the user asks about menstrual cycle status, period dates, next period, or related notes.

Query the user's COROS recovery status. Returns current recovery percentage, recovery level, and estimated full recovery time. Use this when the user asks how recovered they are or how much energy they have left.

Query the user's daily resting heart rate from COROS. Returns the resting heart rate for each day in the specified range. Dates are calculated in the user's COROS timezone. Use this when the user asks about their resting heart rate trend.

Query ONE standalone workout already on the user's COROS training schedule, located by its date and its idInPlan (returned by createScheduledWorkout or scheduleWorkout when it was placed on the schedule, or shown for that standalone workout in queryTrainingSchedule). Use this when the user wants to see or change a workout that is on a specific day (e.g. "tomorrow's run", "the workout on the 18th"). Each scheduled workout is an independent copy: it does NOT change when the workout library original is edited with updateWorkoutDetails, and editing it does not change the library original or other days. Workouts that belong to a training plan are not standalone; for those use Plan ID with queryTrainingPlanDetails. The result contains the scheduled workout summary, the course reconstructed from real data as inline JSON (MCP shape), and an "editable" flag. editable=true means updateScheduledWorkout can fully replace it; editable=false lists the reasons (already completed, date in the past, unsupported sport type or structures beyond MCP's expressible range) - explain those reasons to the user instead of attempting an update. Course JSON carries intensityType on each plain section that has an intensity target, including sets members, not on the course; different sections may use different metrics. A plain section with neither intensityType nor any intensity format fields has unset intensity: it has no intensity target, independently of its target mode. In Course JSON, targetType 4 means free mode and targetValue is omitted; the athlete ends that section with the lap button. Free mode does not mean unset intensity: a free section may still carry its own intensityType and intensity format. Preset targets retain their targetValue. Preserve each section's target mode and intensity, including omitted targetValue for free mode and absent intensity fields for unset intensity, when copying unless the user asks to change them. Course JSON may contain absolute intensity ranges (intensityValueStart/intensityValueEnd in bpm, seconds per kilometer or watts according to that section's intensityType); keep them unchanged when copying - never convert them to zones or percentages. ALWAYS use this before updateScheduledWorkout: copy the course JSON, adjust it, and submit the whole course with the same date and idInPlan. Do not show idInPlan to the user.

Query the user's COROS sleep HRV. Returns the official daily sleep HRV assessment (average HRV, normal range, baseline, and evaluation) together with raw sleep HRV time-series points. Use this single tool when the user asks about sleep HRV, HRV during sleep, HRV on a specific date, recovery status, or why a sleep HRV day is low. Do not calculate the daily HRV average or normal range from raw time-series points; use the official assessment section returned by this tool. Dates are calculated in the user's COROS timezone. Sleep HRV dates are wake-up days — the value for date D comes from the sleep that ended on the morning of D, so 'last night' means TODAY's date; explicit dates from the user should be passed unchanged. Explicit yyyyMMdd dates take priority over recent-days queries.

Query the user's COROS sleep overview. Daily Sleep includes naps; Main Sleep is the selected primary sleep episode. Dates are wake-up days. Returns sleep score, main sleep duration, deep/light/REM ratio, awake time, awake count, main sleep window, and nap windows. Dates are calculated in the user's COROS timezone. IMPORTANT: each night's sleep is attributed to its WAKE-UP date — the sleep of the night of date D is recorded under date D+1. So 'last night' and 'today's sleep' both mean TODAY's date, and 'the night before last' means YESTERDAY's date; never pass yesterday's date for 'last night'. When the user names an explicit date, pass it unchanged — it matches what the COROS app shows for that day; only relative night expressions need this mapping. Use this when the user asks how they slept recently, how they slept last night, or whether they napped.

Query the user's COROS workout records with optional filters such as date range, COROS sport type codes, distance, duration, average pace, and location. Pass numeric sportTypeCodes, not sport names. For broad categories pass all listed codes. COROS sport type codes from dubbo: run=[100 outdoor run,101 indoor run,102 trail run,103 track run,104 hike,105 mountain climb,106 multi-pitch sub climb], bike=[200 outdoor bike,201 indoor bike,202 e-bike,203 gravel bike,204 mountain bike,205 mountain e-bike,299 helmet bike], swim=[300 pool swim,301 open water swim], cardio-strength=[400 gym cardio,401 GPS cardio,402 strength], ski=[500 ski,501 snowboard,502 XC ski,503 alpine touring], sky=[600 fighter], water-row-fishing=[700 rowing,701 indoor row,702 whitewater,704 flatwater,705 windsurfing,706 speedsurfing,707 boat fishing lure,708 shore fishing lure,709 pond fishing lure,710 kayak fishing lure,711 inshore fishing,712 offshore fishing,713 boat fly fishing,714 shore fly fishing,715 surf fishing], climb=[800 indoor single pitch,801 bouldering,802 outdoor climb], walk-fitness=[900 walk,901 jump rope,902 stair climbing,903 elliptical,904 yoga,905 pilates,906 boxing], ball=[1000 badminton,1001 ping pong,1002 basketball,1003 soccer,1004 pickleball,1005 tennis,1006 padel], leisure=[1100 frisbee,1101 skateboard], hybrid fitness=1200, outdoor custom=[9800 custom outdoor ball,9801 custom outdoor leisure,9802 custom outdoor mountain,9803 custom outdoor high altitude,9804 custom outdoor motor vehicle,9805 custom outdoor aquatics,9806 custom outdoor adventure,9807 custom outdoor other], indoor custom=[9900 custom indoor ball,9901 custom indoor strength,9902 custom indoor shape,9903 custom indoor dance,9904 custom indoor other], custom common=9999, multisport=[10000 triathlon,10001 free combine,10002 climb ski,10003 multi-pitch climb], track route=25301, all=65535 or omit sportTypeCodes. Returns date, sport type, location, workout time, distance or sets, average pace or speed, labelId, sportType, and activity startTimestamp/endTimestamp when available. Use the returned timestamps before calling queryCustomActivityLapData for exact windows such as the last 5 minutes. If no date range is given, defaults to the last 7 days.

Query the user's daily average stress level from COROS. Returns the average stress value for each day in the specified range. Dates are calculated in the user's COROS timezone. Use this when the user asks about their stress level or pressure trend.

Query the user's raw stress time series from COROS daily data. Returns stress points with timestamp, timezone, stress value, display score, stress HRV, and stress heart-rate value from a specified yyyyMMdd date range, or from the recent-days window when no date range is given. Dates are calculated in the user's COROS timezone. Use this when the user asks how stress changed today or on a specific date. The query window is capped at 7 days.

Query the user's COROS training load assessment. Returns recent daily comments, short-term load, long-term load, and load ratio. Use this when the user asks whether recent training load is appropriate, too much, or too little.

Query day-by-day details of one COROS training plan by Plan ID (from queryTrainingPlanLibrary or a create/update result). For inspection, any Plan ID returned by queryTrainingPlanLibrary may be queried. For a modification flow, select ONLY an in-progress library result with recordRole=execution and editable=true. A library, completed, unknown, or editable=false record is read-only and must never be passed to updateTrainingPlan; query the editable in-progress execution record instead. If none exists, the user must start or restart the plan in the COROS app first. The window spans at most 28 days (4 weeks). When startDay/endDay are omitted, the window defaults to 4 natural weeks starting from Monday of the current week in the user's COROS timezone, clipped to the plan's date range; plans without anchored dates return their first 4 weeks by dayNo. Query again with explicit startDay/endDay for other windows. The 4-week window limits only the returned day rows; the plan summary and the COMPLETE periodization table always cover the full plan. Each day row carries the MCP dayNo (0-based, relative to plan start), the calendar date, and an ordered courses list. A day may contain multiple courses; each course has its own execute status, score, inline Course JSON reconstructed from real data, and any degradation reasons. Course JSON carries intensityType on each plain section that has an intensity target, including sets members, not on the course; different sections may use different metrics. A plain section with neither intensityType nor any intensity format fields has unset intensity: it has no intensity target, independently of its target mode. In Course JSON, targetType 4 means free mode and targetValue is omitted; the athlete ends that section with the lap button. Free mode does not mean unset intensity: a free section may still carry its own intensityType and intensity format. Preset targets retain their targetValue. Preserve each section's target mode and intensity, including omitted targetValue for free mode and absent intensity fields for unset intensity, when copying unless the user asks to change them. Absolute ranges use bpm, integer seconds per kilometer or watts according to that section's intensityType; do not convert them to zones or percentages. Modification rules: - Editable via MCP is yes: copy ALL course JSON for a changed day, adjust it, and submit that day's entire course list in one updateTrainingPlan request - updating replaces the whole day, never appends or replaces just one course. Submit only the changed days. - Editable via MCP is no: do not call updateTrainingPlan with this Plan ID. - If any course is not losslessly expressible, that day cannot be safely copied for replacement; leave that day unchanged. - If any course is completed, the whole day will be skipped during update; such a day can only be changed in the COROS app. ALWAYS use this before updateTrainingPlan. Do not show Plan ID to the user.

Query the user's COROS training plan library. Every stored plan record is returned separately, so a library original, each completed execution, and the current in-progress execution may all appear with different Plan IDs. Use this before createTrainingPlan (to check for overlapping in-progress plans) and whenever the user asks what training plans they have, including a plain "my training plan(s)" / "查询我的训练计划" request (answer it with this tool's plan list, not with the weekly schedule). For the day-by-day workouts of this week or a date range use queryTrainingSchedule instead. Results are sorted by last update time and returned in pages of at most 50 records; there is no total count. statusList controls the scope and MUST follow the user's wording (product rule): - "all / every / complete list / history / how many plans in total" (Chinese: 全部, 所有, 全量, 完整, 历史, 一共有几个) -> pass statusList=[0,1,2]. - "completed / finished / past plans" (已完成, 完成过的) -> pass [2]. "not started / unstarted / library plans" (未开始, 未执行) -> pass [0]. - plain "my training plans" / "my current plan" with none of those words -> omit statusList; the server then returns in-progress plans only ([1]). When you omit it, say in your answer that only in-progress plans are listed. - Never pass an empty statusList. Other optional filters: planType official/custom/mcp; weeks plan length in weeks. Each record includes recordRole (library/execution/unknown) and editable. Only an in-progress record with recordRole=execution and editable=true may be used with updateTrainingPlan. Never modify a library, completed, unknown, or editable=false record; query for the editable in-progress execution record instead. If none exists, the user must start or restart the plan in the COROS app first. When hasMore=true, call this tool again with the returned nextCursor copied unchanged into cursor and keep the same filters. Continue until hasMore=false when the user asks for all records or an exact count. Plan IDs are internal handles for queryTrainingPlanDetails / updateTrainingPlan. Do not show Plan IDs to the user.

Query the user's COROS training schedule: the day-by-day workouts scheduled for the current week by default, or for a specified date range. Dates are calculated in the user's COROS timezone. Use this when the user asks what they should train today, tomorrow, this week, or on a specific date range, or when you need to locate the workout on a given day that the user wants to change. For "my training plan(s)" / "查询我的训练计划" or which plans the user has (all / in-progress / completed), use queryTrainingPlanLibrary instead. The result includes workouts from training plans and standalone workouts scheduled from the workout library; for workouts from a training plan, use Plan ID with queryTrainingPlanDetails before updateTrainingPlan; to add a new workout on a date, use createScheduledWorkout; to put an existing workout library workout on a date, use scheduleWorkout; to view or modify a standalone workout on its date, use queryScheduledWorkoutDetails then updateScheduledWorkout with its date and idInPlan; to reschedule or remove a standalone workout, use the COROS app. Workouts from training plans include internal Plan ID and idInPlan, standalone workouts include internal idInPlan; do not show these IDs to the user.

Query the user's basic profile information from COROS. Returns height, weight, birthday, and gender. Use this when the user asks about their personal body metrics, profile info, height, weight, age, or gender.

Query one workout from the user's COROS workout library by Workout ID (from queryWorkoutLibrary or createSingleWorkout). This is the library template, not a workout on a specific date; for a workout already on the schedule use queryTrainingSchedule and queryScheduledWorkoutDetails instead. The result contains the workout summary, the course reconstructed from real data as inline JSON (MCP shape), and an "editable" flag. editable=true means updateWorkoutDetails can fully replace it, regardless of where the workout was created; editable=false lists the reasons (e.g. unsupported sport type or structures beyond MCP's expressible range) - explain those reasons to the user instead of attempting an update. Course JSON carries intensityType on each plain section that has an intensity target, including sets members, not on the course; different sections may use different metrics. A plain section with neither intensityType nor any intensity format fields has unset intensity: it has no intensity target, independently of its target mode. In Course JSON, targetType 4 means free mode and targetValue is omitted; the athlete ends that section with the lap button. Free mode does not mean unset intensity: a free section may still carry its own intensityType and intensity format. Preset targets retain their targetValue. Preserve each section's target mode and intensity, including omitted targetValue for free mode and absent intensity fields for unset intensity, when copying unless the user asks to change them. Course JSON may contain absolute intensity ranges (intensityValueStart/intensityValueEnd in bpm, seconds per kilometer or watts according to that section's intensityType); keep them unchanged when copying - never convert them to zones or percentages. ALWAYS use this before updateWorkoutDetails: copy the course JSON, adjust it, and submit the whole course. Making a workout harder or easier, renaming it, or changing sets/targets/intensities all count as updates and go through updateWorkoutDetails - never through createSingleWorkout. Do not show Workout ID to the user.

Query the user's COROS workout library: standalone workout templates not tied to any date, across ALL sport types (including strength, swimming and other existing workouts, even though MCP can only create running/cycling/trail running ones). This is the template library, not the schedule: for the workout on a specific day use queryTrainingSchedule (then queryScheduledWorkoutDetails / updateScheduledWorkout to change it). Results are sorted by last update time, at most 50 rows plus the total count; narrow with filters when more match. Filters (all optional): sportType COROS sport code (1=running, 2=cycling, 3=swimming, 4=strength, 5=trail running, ...); courseType official/custom/mcp. Workout IDs in the result are internal handles for queryWorkoutDetails / updateWorkoutDetails. When the user wants to modify a workout (harden, ease, rename, adjust sets/targets/intensities), find it here, read it with queryWorkoutDetails, then submit the change with updateWorkoutDetails - do not create a new variant with createSingleWorkout. Do not show Workout IDs to the user.

Schedule ONE existing workout from the user's COROS workout library on ONE date. Use this tool only when the user asks to put a workout on a specific day. Use it ONLY for a workout that already exists in the library (any sport, including strength and swimming that MCP cannot create); obtain its Workout ID from queryWorkoutLibrary / queryWorkoutDetails. When the user describes a NEW workout for a date, use createScheduledWorkout instead - do not create a library workout just to schedule it. Any workout in the user's own library can be scheduled, including strength, swimming, and workouts that cannot be edited through MCP. Scheduling copies the full workout into the schedule and leaves the library original unchanged. The date must be a valid yyyyMMdd date, from today through 90 days after today, inclusive, in the user's COROS profile timezone. If that timezone cannot be determined, dates are calculated in UTC and the result includes a note. Call once per date when the user requests several dates; do not pass a date list. If the same workout is already on that day's schedule, no additional copy is added. To add it twice on the same day, use the COROS app. Other workouts already on that day do not block scheduling; tell the user about every other workout listed in the result, including whether it comes from a training plan or is a standalone workout. This tool only adds a workout to the schedule. The result includes the scheduled copy's idInPlan: after scheduling, any change the user wants to the workout on that date must go through queryScheduledWorkoutDetails then updateScheduledWorkout with that date and idInPlan; editing the library original with updateWorkoutDetails does NOT change the scheduled copy. To move or remove it, use the COROS app. Never show internal Workout IDs or idInPlan to the user.

Modify ONE standalone workout that is already on the user's COROS training schedule on a specific date - USE THIS TOOL whenever the user wants to change, harden, ease, rename, re-describe a workout on a given day, or adjust its sets, targets or intensities (e.g. "change tomorrow's run to 50 minutes"). It changes only the scheduled copy on that date; the workout library original is NOT touched. To change the library template instead, use updateWorkoutDetails. Workouts from a training plan are updated with updateTrainingPlan, not with this tool. Never create a new workout with createScheduledWorkout for a modification request. This is FULL REPLACEMENT: the submitted course overwrites the entire scheduled workout, so always start from the current course JSON returned by queryScheduledWorkoutDetails and modify it. ALWAYS call queryScheduledWorkoutDetails first with the same date and idInPlan (idInPlan comes from the createScheduledWorkout / scheduleWorkout result or from queryTrainingSchedule). The updateScheduledWorkout result returns the idInPlan the workout has after saving; if it differs from the one you sent, use the new value for any further change. Only a scheduled workout with editable=true can be updated. The server re-checks ownership, expressibility and completion status and rejects with the reasons otherwise (already completed, date in the past, structures beyond MCP's expressible range); explain those reasons to the user instead of retrying. Moving or removing a scheduled workout is not supported; guide the user to the COROS app. Course rules are identical to createScheduledWorkout: sportType 1=running / 2=cycling / 5=trail running, non-empty sections, interval groups without nesting, meters/seconds integer units, texts in the conversation language. courseName and courseDescription are shown to the athlete in the COROS app EXACTLY as written - plain coaching language only, never JSON field names, enum numbers, or internal labels; sport terms athletes know (Zone 2, FTP, LTHR) are fine. Never set dayNo; the date is given by the date parameter. Preset targetType per sport: running 1 (distance, m) or 2 (time, s); cycling 1 (distance, m) or 2 (time, s), never 3 (climb); trail running 1 (distance) or 3 (climb), not time. For preset trail running warmup/cooldown targets, use distance. Free mode (targetType 4) is also allowed for all supported workout sports, only when explicitly requested; follow the free-mode rule below. - When providing an intensity target, set intensityType separately on each plain section, including sections inside sets: 1=heart rate, 2=pace, 3=% effort threshold pace, 4=power. Different sections of one course may use different metrics. Running allows 1/2/4, cycling 1/4, trail running 1/2/3/4. Do not set intensityType on the course. For trail running, intensityType 2 is measured ground pace without grade adjustment, suitable for flat terrain or controlling actual speed, and supports zones, percent ranges, or absolute ranges. Its zones and percentages use the user's lactate threshold pace. IntensityType 3 is %等强阈值配速 (% effort threshold pace): COROS Effort Pace, grade-adjusted effort on the current slope, expressed only as zones or percent ranges of the same lactate threshold pace, never intensityValueStart/intensityValueEnd. COROS 等强配速 / Effort Pace as an absolute pace in seconds per kilometer is a different intensity type that MCP does not support. If the user asks for 等强配速 / Effort Pace only by name, or gives it in seconds per kilometer, do not call this tool, do not pick a zone for them and do not convert to 2; reply that MCP does not support this intensity type and that only %等强阈值配速 zones or percent ranges (intensityType 3) can be set, then build only if the user asks for that. Use 3 when the user explicitly asks for 等强阈值配速 / % effort threshold pace, or names 等强配速 / Effort Pace together with an explicit zone or percent range; then say in the reply that it is saved as %等强阈值配速. Default to 2 otherwise. State the chosen metric and format in courseDescription. Pace values are seconds per kilometer (6:00/km = 360); absolute values are supported only for intensityType 2. - When a section has intensityType, choose exactly one intensity format and leave the other two formats' fields absent; intensity fields without that section's own intensityType are invalid: (a) sectionIntensity: zone 1-6 (cycling power sections: FTP zone 1-7); (b) intensityPercentStart/intensityPercentEnd: percent of COROS thresholds - intensityType 1 means %LTHR, NOT %maximum heart rate or %heart-rate reserve; 2 means %threshold pace; 3 means %effort threshold pace, using the user's lactate threshold pace as the reference. Do not copy percentages from another basis; if the user's basis is unclear, ask before calling. Integer percents; bounds depend on the section's intensityType: 1 (LTHR) 20 <= start < end <= 120; 2 (threshold pace) and 3 (effort threshold pace) 20 <= start < end <= 140; (c) intensityValueStart/intensityValueEnd: absolute range in physical units - heart rate 30-240 bpm inclusive; pace (intensityType 2 only) 120-1499 integer seconds per kilometer inclusive; % effort threshold pace (intensityType 3) has no absolute form; power 10-2000 W inclusive for running, cycling and trail running. Both absolute endpoints are required. For absolute ranges either order is accepted and equal values are allowed; percent ranges still need start < end. For a single value (e.g. "heart rate 150" or one fixed pace), set both endpoints to that value; do not widen it into a range. - Always provide targetType for each plain section. Normally use a preset distance/time/climb target with a positive targetValue, and normally provide an intensity target as well. - Prefer zones unless the user explicitly gives percentages or physical values. Use requested bpm/pace/W as given, never approximate them as zones or percentages, and never put bpm, pace or watts into the percent fields. - Leave intensity unset ONLY when the user explicitly asks for no intensity target: omit intensityType, sectionIntensity, intensityPercentStart, intensityPercentEnd, intensityValueStart and intensityValueEnd. Do not use unset intensity to avoid choosing an appropriate zone or intensity range. Never send 0 to mean "no intensity": 0 in an intensity field is provided and invalid; unset intensity requires the fields to be absent. - Free mode ONLY when the user explicitly asks for an open-ended section (e.g. warming up until ready): set targetType 4 and omit targetValue. The athlete ends the section with the lap button. Free mode does not mean unset intensity: keep the section's prescribed intensity and apply all intensity rules. Leave intensity unset only under the explicit-request rule above. Free sections are excluded from duration / distance / load estimates. Free mode is allowed for any plain section type, including members inside sets (still sectionType 2/3 only), and a whole course may consist of free sections. Never omit targetType to request free mode. - Power sections (intensityType 4): running and trail running power accepts only absolute ranges, never zones or percent ranges; cycling power allows FTP zones or watts. Percent ranges are never allowed for power in any sport. - % effort threshold pace sections (intensityType 3, trail running only): zones or percent ranges only, never absolute ranges; never send intensityValueStart/intensityValueEnd. Never use 3 to fulfil a request for 等强配速 / Effort Pace given by name alone. - Pace values are total seconds per kilometer (4:30/km = 270; 6:30/mile = 242); a smaller value is a faster pace. Convert mile pace to seconds per kilometer before calling, rounding to the nearest integer. - Preserve an existing section's unset intensity when copying a course unless the user asks to change it. Unset intensity does not change the chosen target mode; preset targets still follow their per-section target limits. Preserve existing free mode and its intensity when copying unless the user asks to change them. - Sections of one course may mix zone, percent and absolute formats as well as intensity metrics; use each section's own intensityType to interpret its values. Interval-group containers must omit intensityType, targetType, targetValue and all intensity format fields; set these on the plain member sections inside sets. Never show idInPlan or internal IDs to the user.

Incrementally update a currently in-progress COROS training plan execution that was created via MCP - including making it SHORTER or LONGER. Day-granular semantics: ONLY the dayNo values present in courseList are touched. Updating a day replaces its whole course list: if a day has workouts A/B and you submit C/D for that day, only C/D remain. Days not mentioned stay unchanged; this is not an append or a single-workout edit. Obtain planId from queryTrainingPlanLibrary and use ONLY an in-progress row with recordRole=execution and editable=true. Never pass the Plan ID of a library, completed, unknown, or editable=false record. If the plan is already running, query its editable in-progress execution record; if none exists, the user must start or restart it in the COROS app first. ALWAYS call queryTrainingPlanDetails on that editable execution record first to read the current plan state, then send only the days that must change. dayNo is 0-based (dayNo 0 = plan start date). Plan length (natural Monday-Sunday weeks, controlled ONLY by planInfo.totalWeeks): - Omit totalWeeks to keep the current length; every dayNo must then stay inside the current plan range. - Pass a SMALLER totalWeeks to shorten (e.g. 12 -> 4): workouts beyond the new final Sunday are removed atomically. The server refuses if completed workouts lie beyond the new end (the message tells the shortest allowed length) or if a running plan would end before today (guide the user to quit the plan in the COROS app instead). - Pass a LARGER totalWeeks to extend: submit only the course entries for newly added workout days; omitted new days are rest days. - WHENEVER totalWeeks changes, the COMPLETE periodization table matching the NEW length is required in the same call. totalWeeks must stay within 4-16. - The FINAL week of the resulting plan must contain at least one workout - this also applies to pure day-granular edits that would clear the last workout of the final week. - For very large edits, split by complete days into consecutive updateTrainingPlan calls in the same conversation; never split one day across calls. Apply changes immediately; never ask the user to complete weeks or return later. Rules: - Multiple workouts are allowed only when explicitly requested, up to 40 per day. For the same dayNo, order is their appearance order in courseList; identical workouts remain separate courses. Send all workouts for that day in one request; never split one day across calls. One described session = one course; never split the warm-up, main set and cool-down of one session into separate courses. List same-day workouts in the order they happen (morning first). - If any workout on a day is completed, the whole day is skipped: all original workouts on that day are kept, including those not started. This applies to both replacement and clearing; other editable days are still processed. Each skipped day is reported once in skippedExecutedDays. - courseList is optional when only changing periodization or length; at least one of courseList / periodization must be present. - A rest entry clears the whole day: send that dayNo as a rest course (sportType 4, empty sections; courseName and courseDescription are still required, e.g. "Rest" / "Recovery day"). Multiple rest entries on the same day clear it only once. Do not combine rest entries with workouts on the same day. Do NOT convert all days to rest to simulate quitting the plan - deleting or quitting a plan is not supported here; guide the user to the COROS app instead. - When phaseInfo.periodization is present it REPLACES the whole periodization table: the first phase starts on the plan start date, later phases start on a Monday, every phase ends on a Sunday, {phaseType 1-6, startDate, endDate, durationWeeks}, total weeks equal to the final plan length. - Course structure rules are identical to createTrainingPlan (sportType 1/2/4/5, non-empty sections for sport courses, empty sections for rest courses, and interval groups). All names and descriptions are shown to the athlete in the COROS app EXACTLY as written - plain coaching language only, never JSON field names, enum numbers, or internal labels; sport terms athletes know (Zone 2, FTP, LTHR) are fine. Preset targetType per sport: running 1 (distance, m) or 2 (time, s); cycling 1 (distance, m) or 2 (time, s), never 3 (climb); trail running 1 (distance) or 3 (climb), not time. For preset trail running warmup/cooldown targets, use distance. Free mode (targetType 4) is also allowed for all supported workout sports, only when explicitly requested; follow the free-mode rule below. - When providing an intensity target, set intensityType separately on each plain section, including sections inside sets: 1=heart rate, 2=pace, 3=% effort threshold pace, 4=power. Different sections of one course may use different metrics. Running allows 1/2/4, cycling 1/4, trail running 1/2/3/4. Do not set intensityType on the course. For trail running, intensityType 2 is measured ground pace without grade adjustment, suitable for flat terrain or controlling actual speed, and supports zones, percent ranges, or absolute ranges. Its zones and percentages use the user's lactate threshold pace. IntensityType 3 is %等强阈值配速 (% effort threshold pace): COROS Effort Pace, grade-adjusted effort on the current slope, expressed only as zones or percent ranges of the same lactate threshold pace, never intensityValueStart/intensityValueEnd. COROS 等强配速 / Effort Pace as an absolute pace in seconds per kilometer is a different intensity type that MCP does not support. If the user asks for 等强配速 / Effort Pace only by name, or gives it in seconds per kilometer, do not call this tool, do not pick a zone for them and do not convert to 2; reply that MCP does not support this intensity type and that only %等强阈值配速 zones or percent ranges (intensityType 3) can be set, then build only if the user asks for that. Use 3 when the user explicitly asks for 等强阈值配速 / % effort threshold pace, or names 等强配速 / Effort Pace together with an explicit zone or percent range; then say in the reply that it is saved as %等强阈值配速. Default to 2 otherwise. State the chosen metric and format in courseDescription. Pace values are seconds per kilometer (6:00/km = 360); absolute values are supported only for intensityType 2. - When a section has intensityType, choose exactly one intensity format and leave the other two formats' fields absent; intensity fields without that section's own intensityType are invalid: (a) sectionIntensity: zone 1-6 (cycling power sections: FTP zone 1-7); (b) intensityPercentStart/intensityPercentEnd: percent of COROS thresholds - intensityType 1 means %LTHR, NOT %maximum heart rate or %heart-rate reserve; 2 means %threshold pace; 3 means %effort threshold pace, using the user's lactate threshold pace as the reference. Do not copy percentages from another basis; if the user's basis is unclear, ask before calling. Integer percents; bounds depend on the section's intensityType: 1 (LTHR) 20 <= start < end <= 120; 2 (threshold pace) and 3 (effort threshold pace) 20 <= start < end <= 140; (c) intensityValueStart/intensityValueEnd: absolute range in physical units - heart rate 30-240 bpm inclusive; pace (intensityType 2 only) 120-1499 integer seconds per kilometer inclusive; % effort threshold pace (intensityType 3) has no absolute form; power 10-2000 W inclusive for running, cycling and trail running. Both absolute endpoints are required. For absolute ranges either order is accepted and equal values are allowed; percent ranges still need start < end. For a single value (e.g. "heart rate 150" or one fixed pace), set both endpoints to that value; do not widen it into a range. - Always provide targetType for each plain section. Normally use a preset distance/time/climb target with a positive targetValue, and normally provide an intensity target as well. - Prefer zones unless the user explicitly gives percentages or physical values. Use requested bpm/pace/W as given, never approximate them as zones or percentages, and never put bpm, pace or watts into the percent fields. - Leave intensity unset ONLY when the user explicitly asks for no intensity target: omit intensityType, sectionIntensity, intensityPercentStart, intensityPercentEnd, intensityValueStart and intensityValueEnd. Do not use unset intensity to avoid choosing an appropriate zone or intensity range. Never send 0 to mean "no intensity": 0 in an intensity field is provided and invalid; unset intensity requires the fields to be absent. - Free mode ONLY when the user explicitly asks for an open-ended section (e.g. warming up until ready): set targetType 4 and omit targetValue. The athlete ends the section with the lap button. Free mode does not mean unset intensity: keep the section's prescribed intensity and apply all intensity rules. Leave intensity unset only under the explicit-request rule above. Free sections are excluded from duration / distance / load estimates. Free mode is allowed for any plain section type, including members inside sets (still sectionType 2/3 only), and a whole course may consist of free sections. Never omit targetType to request free mode. - Power sections (intensityType 4): running and trail running power accepts only absolute ranges, never zones or percent ranges; cycling power allows FTP zones or watts. Percent ranges are never allowed for power in any sport. - % effort threshold pace sections (intensityType 3, trail running only): zones or percent ranges only, never absolute ranges; never send intensityValueStart/intensityValueEnd. Never use 3 to fulfil a request for 等强配速 / Effort Pace given by name alone. - Pace values are total seconds per kilometer (4:30/km = 270; 6:30/mile = 242); a smaller value is a faster pace. Convert mile pace to seconds per kilometer before calling, rounding to the nearest integer. - Preserve an existing section's unset intensity when copying a course unless the user asks to change it. Unset intensity does not change the chosen target mode; preset targets still follow their per-section target limits. Preserve existing free mode and its intensity when copying unless the user asks to change them. - Sections of one course may mix zone, percent and absolute formats as well as intensity metrics; use each section's own intensityType to interpret its values. Interval-group containers must omit intensityType, targetType, targetValue and all intensity format fields; set these on the plain member sections inside sets. - Language: keep texts in the conversation language. Units: meters / seconds. The response is a change summary (updated / cleared / skipped-executed / truncated days, previous and new length); each day list is unique and sorted in ascending dayNo order. Report skipped executed days and truncated days to the user honestly. Never show internal Plan IDs to the user.

Modify an existing workout in the user's COROS workout library - USE THIS TOOL whenever the user wants to change, harden, ease, rename, re-describe a library workout, or adjust its sets, targets or intensities. Modification IS supported; never tell the user a workout cannot be modified without checking queryWorkoutDetails first, and never create a new variant via createSingleWorkout for a modification request. LIBRARY ONLY: this changes the workout library template. Copies already placed on the schedule (via scheduleWorkout or the COROS app) are independent and are NOT updated by this tool. When the user wants to change the workout on a specific day (e.g. "tomorrow's run", "the workout on the 18th"), use queryTrainingSchedule to find that day's standalone workout and then queryScheduledWorkoutDetails / updateScheduledWorkout instead; if you do use this tool, tell the user that already scheduled copies keep their old content. This is FULL REPLACEMENT: the submitted course overwrites the entire original workout, so always start from the current course JSON returned by queryWorkoutDetails and modify it. ALWAYS call queryWorkoutDetails first. Any workout of the user with editable=true can be updated regardless of where it was created - editable depends only on whether the workout's CURRENT content is fully expressible in the MCP course shape, not on its origin. The server re-checks ownership and expressibility and rejects with the reasons otherwise; explain those reasons to the user instead of retrying. Deleting a workout is not supported; guide the user to the COROS app for deletion. Course rules are identical to createSingleWorkout: sportType 1=running / 2=cycling / 5=trail running, non-empty sections, interval groups without nesting, meters/seconds integer units, texts in the conversation language. courseName and courseDescription are shown to the athlete in the COROS app EXACTLY as written - plain coaching language only, never JSON field names, enum numbers, or internal labels; sport terms athletes know (Zone 2, FTP, LTHR) are fine. Library workouts carry no date: never set dayNo, and this tool never schedules anything. Preset targetType per sport: running 1 (distance, m) or 2 (time, s); cycling 1 (distance, m) or 2 (time, s), never 3 (climb); trail running 1 (distance) or 3 (climb), not time. For preset trail running warmup/cooldown targets, use distance. Free mode (targetType 4) is also allowed for all supported workout sports, only when explicitly requested; follow the free-mode rule below. - When providing an intensity target, set intensityType separately on each plain section, including sections inside sets: 1=heart rate, 2=pace, 3=% effort threshold pace, 4=power. Different sections of one course may use different metrics. Running allows 1/2/4, cycling 1/4, trail running 1/2/3/4. Do not set intensityType on the course. For trail running, intensityType 2 is measured ground pace without grade adjustment, suitable for flat terrain or controlling actual speed, and supports zones, percent ranges, or absolute ranges. Its zones and percentages use the user's lactate threshold pace. IntensityType 3 is %等强阈值配速 (% effort threshold pace): COROS Effort Pace, grade-adjusted effort on the current slope, expressed only as zones or percent ranges of the same lactate threshold pace, never intensityValueStart/intensityValueEnd. COROS 等强配速 / Effort Pace as an absolute pace in seconds per kilometer is a different intensity type that MCP does not support. If the user asks for 等强配速 / Effort Pace only by name, or gives it in seconds per kilometer, do not call this tool, do not pick a zone for them and do not convert to 2; reply that MCP does not support this intensity type and that only %等强阈值配速 zones or percent ranges (intensityType 3) can be set, then build only if the user asks for that. Use 3 when the user explicitly asks for 等强阈值配速 / % effort threshold pace, or names 等强配速 / Effort Pace together with an explicit zone or percent range; then say in the reply that it is saved as %等强阈值配速. Default to 2 otherwise. State the chosen metric and format in courseDescription. Pace values are seconds per kilometer (6:00/km = 360); absolute values are supported only for intensityType 2. - When a section has intensityType, choose exactly one intensity format and leave the other two formats' fields absent; intensity fields without that section's own intensityType are invalid: (a) sectionIntensity: zone 1-6 (cycling power sections: FTP zone 1-7); (b) intensityPercentStart/intensityPercentEnd: percent of COROS thresholds - intensityType 1 means %LTHR, NOT %maximum heart rate or %heart-rate reserve; 2 means %threshold pace; 3 means %effort threshold pace, using the user's lactate threshold pace as the reference. Do not copy percentages from another basis; if the user's basis is unclear, ask before calling. Integer percents; bounds depend on the section's intensityType: 1 (LTHR) 20 <= start < end <= 120; 2 (threshold pace) and 3 (effort threshold pace) 20 <= start < end <= 140; (c) intensityValueStart/intensityValueEnd: absolute range in physical units - heart rate 30-240 bpm inclusive; pace (intensityType 2 only) 120-1499 integer seconds per kilometer inclusive; % effort threshold pace (intensityType 3) has no absolute form; power 10-2000 W inclusive for running, cycling and trail running. Both absolute endpoints are required. For absolute ranges either order is accepted and equal values are allowed; percent ranges still need start < end. For a single value (e.g. "heart rate 150" or one fixed pace), set both endpoints to that value; do not widen it into a range. - Always provide targetType for each plain section. Normally use a preset distance/time/climb target with a positive targetValue, and normally provide an intensity target as well. - Prefer zones unless the user explicitly gives percentages or physical values. Use requested bpm/pace/W as given, never approximate them as zones or percentages, and never put bpm, pace or watts into the percent fields. - Leave intensity unset ONLY when the user explicitly asks for no intensity target: omit intensityType, sectionIntensity, intensityPercentStart, intensityPercentEnd, intensityValueStart and intensityValueEnd. Do not use unset intensity to avoid choosing an appropriate zone or intensity range. Never send 0 to mean "no intensity": 0 in an intensity field is provided and invalid; unset intensity requires the fields to be absent. - Free mode ONLY when the user explicitly asks for an open-ended section (e.g. warming up until ready): set targetType 4 and omit targetValue. The athlete ends the section with the lap button. Free mode does not mean unset intensity: keep the section's prescribed intensity and apply all intensity rules. Leave intensity unset only under the explicit-request rule above. Free sections are excluded from duration / distance / load estimates. Free mode is allowed for any plain section type, including members inside sets (still sectionType 2/3 only), and a whole course may consist of free sections. Never omit targetType to request free mode. - Power sections (intensityType 4): running and trail running power accepts only absolute ranges, never zones or percent ranges; cycling power allows FTP zones or watts. Percent ranges are never allowed for power in any sport. - % effort threshold pace sections (intensityType 3, trail running only): zones or percent ranges only, never absolute ranges; never send intensityValueStart/intensityValueEnd. Never use 3 to fulfil a request for 等强配速 / Effort Pace given by name alone. - Pace values are total seconds per kilometer (4:30/km = 270; 6:30/mile = 242); a smaller value is a faster pace. Convert mile pace to seconds per kilometer before calling, rounding to the nearest integer. - Preserve an existing section's unset intensity when copying a course unless the user asks to change it. Unset intensity does not change the chosen target mode; preset targets still follow their per-section target limits. Preserve existing free mode and its intensity when copying unless the user asks to change them. - Sections of one course may mix zone, percent and absolute formats as well as intensity metrics; use each section's own intensityType to interpret its values. Interval-group containers must omit intensityType, targetType, targetValue and all intensity format fields; set these on the plain member sections inside sets. Never show internal Workout IDs to the user.

Upload a GPX or KML route file to the user's COROS account so it appears in the Routes list of the COROS app and can be synced to the watch for navigation. Use this tool when the user provides a GPX or KML file (or its XML text) and asks to import it as a COROS route. Pass the complete, unmodified XML text of the file in fileContent and the original file name (with .gpx or .kml extension) in fileName. Do not summarize, truncate, or reformat the XML. The file must contain at least two track points. Always set routeType: 1 for cycling routes, 2 for on-foot routes. COROS routes only have these two types; the type is shown in the COROS app and cannot be changed through this tool. COROS processes route files asynchronously: a successful result means the file was accepted, and the route usually appears in the COROS app within a few minutes. If the same file was already imported and that route still exists in the COROS app, or is still being processed, the upload is rejected. After the user deletes the existing route in the app, the same file can be imported again.