Pacelab Intervals

Create a structured interval workout in Pacelab. If the user has connected their Pacelab account, the workout is saved straight to their library and appears in the app. Otherwise a public share link is returned that they can import. Field-level rules (ranges, which block type needs which field) are in the schema — follow them rather than guessing. A few things the schema cannot say: - Each exercise needs EITHER reps OR duration_sec, never both. Use reps for rounds/fortime/amrap; duration_sec for tabata/circuit/timed. - For EMOM, set rounds to the total minutes and give each exercise a station_index for the minute it runs in. - Set order_index on every block and every exercise, starting at 0. - Call get_workout_formats first if unsure which block type fits. Challenges: pass challenge_ends_at to make this a shareable challenge instead of a plain workout. Anyone who opens the share link can post a result to a shared leaderboard until that deadline, then the board freezes. Use it when the user says things like "make it a challenge", "for me and my friends", or names a deadline. Always give them the share URL afterwards — a challenge nobody can join is pointless. Do not generate rehabilitation, injury-recovery, or pregnancy-specific programming. Suggest the user consult a qualified professional instead. Returns a summary with the share URL and deep link. When saved to a library it also returns workout_local_id, which schedule_workout needs. Example — 8-round Tabata: blocks=[{ "type": "tabata", "rounds": 8, "work_sec": 20, "rest_sec": 10, "order_index": 0, "exercises": [ {"exercise_name": "Burpees", "duration_sec": 20, "order_index": 0} ] }] Example — 10-minute AMRAP: blocks=[{ "type": "amrap", "rounds": 1, "work_sec": 600, "order_index": 0, "exercises": [ {"exercise_name": "Push-ups", "reps": 10, "order_index": 0}, {"exercise_name": "Squats", "reps": 15, "order_index": 1} ] }]

create_workout

Read the leaderboard for a shared workout or challenge. Use this to answer "who's winning?", "where am I on the board?", or to summarise how a challenge is going. Boards are public to anyone with the share link, so this works with or without a connected account — though connecting lets the result mark which row is the user's own. Only each person's best entry is listed. Ranking depends on the workout's format: fixed-window formats score on reps, everything else on time. Report the ranking basis when summarising, so "first place" is meaningful.

get_challenge_results

Fetch one workout in full, including every block and exercise. Call this before update_workout: read the workout, change what the user asked for, then pass the whole blocks list back. Requires a connected Pacelab account.

get_workout

Return a quick-reference guide for all Pacelab workout block types, categories, and equipment options. Use this before create_workout to understand which block type fits the user's goal, and what values are valid.

get_workout_formats

Read the user's completed workout history and training statistics. Use this before create_workout when the user asks for a workout "based on my history", a progression, something harder/easier than usual, or a plan that fits their routine. It reveals training frequency, typical session length, preferred block formats, and which workouts they repeat. Requires a connected Pacelab account (OAuth). Returns only the requesting user's own data. Args: limit: How many recent sessions to include (1–50, default 20). Stats always cover the user's full history regardless of limit. Returns: A summary with lifetime stats (total sessions, training time, current streak, personal records), a breakdown of most-used block formats and most-repeated workouts, and a list of recent sessions with date, duration, rounds completed, and difficulty rating where recorded.

get_workout_history

List the workouts in the user's Pacelab library, newest first. Use this to answer questions about what they already have, to find a workout to modify, or before creating something new so you don't duplicate an existing one. Blocks are omitted here to keep the response small — call get_workout for the full structure. Requires a connected Pacelab account.

list_my_workouts

Schedule a workout in the user's Pacelab calendar. Only works when the user has connected their Pacelab account via OAuth. Use the workout_local_id returned by create_workout to schedule it. Args: workout_local_id: The local_id returned by create_workout. Required to link the scheduled entry to the workout in the app. title: Workout title (use the same title as the created workout). date: Date to schedule in YYYY-MM-DD format (e.g. "2026-06-08"). time: Time of day in HH:MM 24h format (e.g. "07:00"). Defaults to 07:00. notes: Optional note shown on the scheduled entry (e.g. "After morning run"). Returns: Confirmation with the scheduled date and time.

schedule_workout

Replace an existing workout in the user's library. This overwrites the whole workout, so call get_workout first, apply the user's change to the blocks you get back, and send the complete list. Sending only the block you changed would delete the others. Prefer this over create_workout when the user says things like "make that 30 seconds" or "add a cooldown" about a workout that already exists — otherwise they end up with duplicates. Requires a connected Pacelab account.

update_workout