MoveMate: Gym Workout Tracker

Returns one specific MoveMate workout by its exact workout_id and renders the same workout card as list_workouts. Use this whenever the user asks to show, open, or display a particular workout already identified earlier in the conversation, especially one returned by create_planned_workout, update_planned_workout, list_planned_workouts, or list_workouts. Do not answer with only a text summary when a valid workout_id is available.

get_workout

Returns a workout's full contents — every exercise with its exercise_id, exercise_type, sets and targets, rest, notes and superset grouping — in exactly the shape update_custom_workout, update_planned_workout and create_custom_workout accept. Call it before changing a workout's exercises: those tools replace the whole list, so start from this one, change what the user asked for, and send the rest back unchanged. Works for the user's saved workouts, library workouts and the workouts of scheduled sessions (workout_id from list_workouts, list_planned_workouts or an earlier write). To show the user a workout card instead, use get_workout.

get_workout_details

What's coming up — so the model can answer that and avoid double-booking.

list_planned_workouts

Browses MoveMate's workout catalog — both the shared library and the user's own custom workouts, together by default. Use this to find an existing workout to schedule (pass its workout_id to create_planned_workout) rather than building one from scratch, to find one of the user's saved workouts to change (update_custom_workout, after reading it with get_workout_details), to browse by body focus ("give me a leg workout" — use category), or to look up one the user just opened in the app by its workout_id. Not the user's calendar (see list_planned_workouts) and not training history (see get_recent_workouts).

list_workouts

Records workouts the user has ALREADY FINISHED into their MoveMate history — "log yesterday's workout: bench 4x8 at 80 kg, squats 3x5 at 100", or a short history the user is moving over from notes or another app. Send whole sessions with the sets actually done, up to 20 workouts per call. Not a live tracker: if the user wants to log set by set while training, point them to the workout tracker in the MoveMate app (rest timer, weight suggestions) instead of calling this after every set. Dates: a workout from before the user joined MoveMate is history and may have any date; a workout from since they joined must be from today or the last 14 days. For a future date use create_planned_workout. At most 300 past workouts can be moved in through chat in total; for a longer history or an export file from another app (Hevy, Strong and others), tell the user about the workout import in the MoveMate app instead. Every exercise_id must come from search_exercises or create_custom_exercise — never invented. Each exercise is measured by its exercise_type (from search_exercises); send the fields that type uses: default = weight and reps (most strength work, and bodyweight work with reps such as pull-ups or hill sprints); time = duration only (planks, dead hangs, skipping); time_weight = duration and weight (weighted plank, farmer hold); distance_time = distance and duration (outdoor running, cycling or swimming, rowing machine, SkiErg — anything whose monitor shows distance rather than km/h); weight_distance = weight and distance (farmer walk, sled push); cardio_machine = speed in km/h, the machine level (incline or resistance) and duration — treadmill, stationary bike, stepmill; distance is derived from speed and time. Continuous cardio (cardio_machine, distance_time) is ONE set per session — a 20-minute treadmill walk is a single set of 1200 seconds, not three. If you had to guess any exercise, weight, rep count or date, read the workouts back and get the user's agreement before calling. Safe to retry: a workout already in the history (same date, start time and title) is not added twice. Free accounts can finish 3 workouts in total (in the app and here together); workouts from before they joined do not count. A refusal for that reason says so and must not be retried.

log_completed_workouts

Searches MoveMate's exercise library (including the user's own custom exercises). The model must only compose workouts from exercises returned here — never invented ones. Each result carries an exercise_type saying how that movement is measured (reps, time, distance, or speed and level on a cardio machine) — it decides which target fields create_planned_workout will accept for it, so read it before writing sets.

search_exercises

Changes a workout that has not been done yet — reschedule it, rename it, or replace its exercise list. Works on an upcoming session and on one the app marked skipped because its time passed; rescheduling a skipped session makes it upcoming again. A finished workout cannot be changed. Pass only the fields you want to change; anything omitted stays as-is. `exercises`, if given, replaces the whole list — to add an exercise, pass the existing ones plus the new one; to remove one, pass the list without it. Read the current list with get_workout_details first; never rebuild it from memory. Because the list is replaced wholesale, any superset_group labels left out are removed too. A session's title, notes and exercises belong to the workout it uses: if that workout is one of the user's saved workouts, the change applies to it and to every other session using it, as editing it in the app does; if it is a MoveMate library workout, which cannot be changed, the user's sessions of it switch to their own edited copy. Rescheduling and reminders only ever affect the one session. When the same workout is scheduled more than once, pass session_date to pick the session. A workout can mix strength and conditioning freely: each exercise is measured by its own exercise_type (from search_exercises), so a run, a skipping round or a set of sprints sits in the same list as the lifts — send the targets that type accepts.

update_planned_workout

Changes one of the user's own saved workouts ("My workouts" in the app) — rename it, change its note, or replace its exercise list — the same as editing it in the app. Every scheduled session that uses this workout shows the change too, including upcoming ones; the response says how many. Library workouts cannot be changed: to make a personal version, save one with create_custom_workout. Pass only the fields you want to change; anything omitted stays as-is. `exercises`, if given, replaces the whole list — to add an exercise, pass the existing ones plus the new one in the right position; to remove one, pass the list without it. ALWAYS read the current list with get_workout_details first and send it back with your change — never rebuild it from memory, or the exercises, sets and weights you leave out are lost. Confirm the change with the user before calling. Each exercise is measured by its own exercise_type — send the targets that type accepts.

update_custom_workout