Lion Lift

Create a structured interval running workout — warmup, repeatable work/recovery blocks, cooldown, each step with an optional pace/heart- rate/power/cadence alert. Mirrors Apple's own WorkoutKit object model field-for-field (CustomWorkout/WorkoutStep/IntervalBlock/WorkoutGoal/ WorkoutAlert). IMPORTANT — confirm before calling: describe the full workout back to the user in plain language (warmup, every block's work/recovery and iteration count, any target pace/heart rate/etc., cooldown, indoor vs outdoor, and the scheduled date/time) and get their explicit confirmation first. This writes to their real account immediately and irreversibly from this server's own perspective — there's no "undo" tool. This does NOT put the workout on Apple Fitness/the Watch by itself — it only creates a pending record. WorkoutKit scheduling is a local, on-device operation this server has no way to perform remotely, so the user still has to open Lion Lift and tap "Sync" themselves (Workouts tab → Run → Sync Workouts). Tell them that's the next step. display_name: come up with a short, specific, memorable title based on what this workout actually is — e.g. "50m Sprint Repeats", "Tempo Ladder", "5x800 Negative Split" — not a generic label like "Interval Run" every time. Shown as this workout's title on the Watch/Fitness app and in Lion Lift's own Sync Workouts list, where several of these can be listed side by side, so it needs to read as distinct from the user's other workouts at a glance, not just descriptive in isolation. scheduled_for: "YYYY-MM-DDTHH:MM", 24-hour, the user's local time — when they intend to do this run. Confirm "today"/"tomorrow" explicitly rather than assuming a timezone, same as schedule_lift. location: "outdoor" (default, GPS-based — required for any pace/speed alert) or "indoor" (treadmill — pace alerts aren't meaningful without GPS; use a heart-rate or cadence alert instead for an indoor workout). blocks: at least one IntervalBlockInput. Each has: - iterations (int, default 1): how many times the work/recovery pair repeats. - work (required) / recovery (optional): each a StepInput — see below. warmup / cooldown: optional single StepInputs (no iteration count). A StepInput is: {goal, alert?, display_name?}. - display_name: optional label for that one step, e.g. "800m Repeat". - goal (a GoalInput): {type, ...}. type is one of: "open" — no fields needed, the user advances it manually. "time" — needs seconds (float). "distance" — needs miles (float). "energy" — needs kilocalories (float). - alert (an AlertInput, optional): {type, ...}. type is one of: "heartRateZone" — needs zone (int, e.g. 1-5). "heartRateRange" — needs bpm_low, bpm_high. "paceThreshold" — needs pace_sec_per_mile, optional metric ("average"/"current", default "average"). "paceRange" — needs pace_sec_per_mile_low, pace_sec_per_mile_high (lower = faster), optional metric. "powerZone" — needs zone (int). "powerRange" — needs watts_low, watts_high. "powerThreshold" — needs watts. "cadenceRange" — needs spm_low, spm_high (steps/min). "cadenceThreshold" — needs spm (steps/min). Example — "5x800m at 6:30-7:00/mile pace, 2 min jog recovery, with a 10 minute warmup and 5 minute cooldown": warmup = {"goal": {"type": "time", "seconds": 600}} blocks = [{ "iterations": 5, "work": { "goal": {"type": "distance", "miles": 0.5}, "alert": {"type": "paceRange", "pace_sec_per_mile_low": 390, "pace_sec_per_mile_high": 420}, "display_name": "800m Repeat", }, "recovery": {"goal": {"type": "time", "seconds": 120}, "display_name": "Jog Recovery"}, }] cooldown = {"goal": {"type": "time", "seconds": 300}}

schedule_interval_run

Schedule a new lift workout. This is the only write this server can do, deliberately narrow in scope — create-a-scheduled-lift only, never update/complete/delete. Mirrors exactly what the app itself writes when scheduling a workout (ManualWorkoutEntryView.saveWorkout() / LiftCompletionService.complete()), so a workout scheduled here behaves identically to one scheduled from the app — shows up in today's-workouts queries, syncs to the watch on its next check-in, etc. IMPORTANT — confirm before calling: always show the user the exact workout you're about to schedule (date, every exercise, every set's weight/reps, and notes if any) and get their explicit confirmation first. This tool writes to their real, live workout schedule immediately and irreversibly from its own perspective (there's no "undo" tool) — never call it speculatively or as part of just thinking out loud with the user. scheduled_date: a plain calendar date, "YYYY-MM-DD" (e.g. "2026-09-20") — not a datetime, since scheduling is a whole-day concept. Confirm "today" with the user rather than assuming a timezone if the date is ambiguous (e.g. requested near midnight) — this server has no configured local timezone to resolve that for you. Every other date-shaped field the app relies on (the display string, date_ymd, date_ts, weekId) is derived from this single input, matching exactly what the app's own code computes for it — status is always "scheduled" and created_at is always "now," neither is a parameter. lifts: exercise name + sets (weight in lbs, reps) per exercise — call list_known_exercises() first for real exercise names instead of inventing new ones. Muscle group(s) are auto-classified from these exercise names, exactly like the app itself now does — there's no muscle_group parameter to set. notes: optional, defaults to empty. Once this lift is actually completed, its `lifts` field gets overwritten with the real final sets — the planned weight/reps you pass here stop being visible there. A frozen copy of what you scheduled survives separately in `original_lift_plan` (set automatically, nothing to pass for it), so a completed lift can later be compared planned-vs-actual the same way it works for scheduled runs/swims/rides.

schedule_lift

Create a structured POOL swimming workout — warmup, repeatable work/recovery blocks, cooldown, each step with an optional heart-rate/ power/cadence alert and an optional stroke-type label — mirroring Apple's own WorkoutKit object model for pool swimming specifically (open-water swimming isn't supported by this tool). IMPORTANT — confirm before calling: describe the full workout back to the user in plain language (warmup, every block's work/recovery and iteration count, any stroke types, any target heart rate/etc., cooldown, and the scheduled date/time) and get their explicit confirmation first. This writes to their real account immediately and irreversibly from this server's own perspective — there's no "undo" tool. This does NOT put the workout on Apple Fitness/the Watch by itself — it only creates a pending record. WorkoutKit scheduling is a local, on-device operation this server has no way to perform remotely, so the user still has to open Lion Lift and tap "Sync" themselves (Workouts tab → Swim → Sync Workouts). Tell them that's the next step. Pool length and pool-vs-open-water are deliberately not parameters here — Apple's own Workout app asks the swimmer for pool length and location when they actually start the workout, and auto-scales distances/times to match, so there's nothing for this tool to set. display_name: come up with a short, specific, memorable title based on what this workout actually is (e.g. "Threshold 100s", "IM Ladder") — not a generic label like "Swim Workout" every time. Shown as this workout's title on the Watch/Fitness app and in Lion Lift's own Sync Workouts list, where several of these can be listed side by side. scheduled_for: "YYYY-MM-DDTHH:MM", 24-hour, the user's local time — when they intend to do this swim. Confirm "today"/"tomorrow" explicitly rather than assuming a timezone, same as schedule_lift. blocks: at least one SwimIntervalBlockInput. Each has: - iterations (int, default 1): how many times the work/recovery pair repeats. - work (required) / recovery (optional): each a SwimStepInput — see below. warmup / cooldown: optional single SwimStepInputs (no iteration count). A SwimStepInput is: {goal, alert?, display_name?}. - display_name: optional label for that one step — either descriptive (e.g. "Kick Set") or the stroke type (e.g. "Freestyle", "Backstroke", "Breaststroke", "Butterfly", "IM"). - goal (a SwimGoalInput): {type, ...}. type is one of: "open" — no fields needed, manual advance. "time" — needs seconds (float). "distance" — needs meters (float). "energy" — needs kilocalories (float). "poolSwimDistanceWithTime" — needs BOTH meters and seconds — a combined distance-and-time target (e.g. "100m within 1:30"); the step only advances once both are met, not just whichever comes first. - alert (a SwimAlertInput, optional): {type, ...}. No pace/speed option — there's no GPS in a pool. type is one of: "heartRateZone" — needs zone (int, e.g. 1-5). "heartRateRange" — needs bpm_low, bpm_high. "powerZone" — needs zone (int). "powerRange" — needs watts_low, watts_high. "powerThreshold" — needs watts. "cadenceRange" — needs spm_low, spm_high (strokes/min). "cadenceThreshold" — needs spm (strokes/min). Example — "10x100m freestyle on a 1:30 interval, with a 200m warmup and 200m cooldown": warmup = {"goal": {"type": "distance", "meters": 200}} blocks = [{ "iterations": 10, "work": { "goal": {"type": "poolSwimDistanceWithTime", "meters": 100, "seconds": 90}, "display_name": "Freestyle", }, }] cooldown = {"goal": {"type": "distance", "meters": 200}}

schedule_pool_swim_workout