Reps

Returns the user's currently active training plan, all of its routines and their exercises, plus a `next_routine` hint (today for fixed-day plans, next-in-rotation for rotating).

get_training_plan

Adds a movement the exercise library doesn't have to the user's own library — a gym-specific machine, a variation, anything `get_exercise_library` comes back empty for. Search the library FIRST; this returns `already_exists` (with the match) rather than creating a duplicate. Fill in `muscle_groups` and `equipment` from what the user described, and tell the user in one sentence what you assumed. The exercise is created at once, and the returned `slug` / `exercise_id` work in `save_routine`, `save_plan` and `edit_routine` straight away. To change it later, use `update_custom_exercise`.

add_custom_exercise

Edits one of the user's OWN custom exercises in place: rename it, re-file it under other `muscle_groups` / `equipment` / `type`, or set its `notes` — its how-to, the step-by-step instructions shown on the exercise, one step per line. Find the slug with `get_exercise_library` (only `is_custom: true` rows qualify; built-ins return `not_custom`). Send only the fields that change. Applied at once — no confirmation step — so use it when the user asks for the change or has just agreed to it, and say in one sentence what you changed.

update_custom_exercise

Changes an existing routine: its exercises, sets, targets, order or name. First call `get_routines` for its `routine_id`, current exercises and `updated_at`. This writes straight away: tell the user exactly what will change (what is added, removed or adjusted) and wait for an explicit yes in this conversation. Send the FULL end state in `exercises`, every exercise the routine should contain, in order; anything left out is removed. Pass the `updated_at` you read as `base_updated_at`: if the routine changed in the Reps app since, nothing is saved and the result is `routine_changed`. The result lists the routine as it now stands. The change shows up in the Reps app after its next sync (up to 5 minutes) or when the app is reopened.

edit_routine

Browse the exercise catalog visible to the user (built-ins + their custom exercises). Filter by `search` (substring on name), `muscle_group`, and/or `equipment`. Returns canonical `slug`s usable in other tools, and each exercise's `note` — the user's own note on it, or null.

get_exercise_library

Time-series of a single exercise (one data point per day). Default range 90 days. Use for prompts like "how has my bench progressed?". `metric` selects max_weight (default), estimated_1rm (Epley), or volume.

get_exercise_progression

Personal records the app has tracked for the user. Each record has a `record_type` ('max_weight' kg, 'max_reps' count, 'max_volume' weight×reps, or 'estimated_1rm' kg) and a numeric `value`. Filter by `exercise_slug` for one exercise, by `kind` for one record type, or omit both for everything. Use for "what are my PRs?".

get_personal_records

Saves a new routine to the user's Reps library. This writes straight away: first describe the routine to the user in plain words (its name and each exercise with sets, reps and weight) and wait for an explicit yes in this conversation. Reference exercises by `exercise_slug` or `exercise_id` from `get_exercise_library`. An exercise the library does not have is refused with `candidates`: retry with one only when it is clearly what the user meant, otherwise ask. `target_reps` is a rep count (max 50); for a timed hold or cardio (plank, wall sit, rowing) leave it out and put the target time in `notes` ("45 s"). The result lists what was saved by name. The routine shows up in the Reps app after its next sync (up to 5 minutes) or when the app is reopened; say so. Use this for prompts like "build me a push routine for 60 minutes".

save_routine

Saves a whole training plan in one call: the routines it defines, the plan itself and which routine runs when. This writes straight away: first describe the plan to the user (its routines, their exercises and the schedule) and wait for an explicit yes in this conversation. `schedule_type` is "rotation" (routines run in order, no weekdays) or "fixed_days" (every routine needs a distinct `day_of_week`, 1 = Monday … 7 = Sunday). To reuse a routine the user already has, pass its `routine_id` from `get_routines`: it is LINKED, not copied. Otherwise give its `exercises`, with slugs or ids from `get_exercise_library`. For a plan the user brought (a photo, a PDF, a spreadsheet or pasted text), read it yourself, look every exercise up, and add what the library lacks with `add_custom_exercise` before saving; an unknown exercise is refused with `candidates`. The plan becomes the active one unless you pass `activate: false`; that stops the previously active plan, which the result names in `replaced_plan`, so tell the user. It shows up in the Reps app after its next sync (up to 5 minutes) or when the app is reopened; say so.

save_plan

Browse the user's saved routines (across all plans, and routines not in any plan). Each routine includes its exercises with `default_sets` and `notes`, plus an `in_plans` list showing which plans (if any) reference it and on which `day_of_week`. Filter by `routine_id` for one routine, `search` for a substring on the name, or omit both for all. Use this for prompts like "show me my Push routine" or "what routines do I have?". Each routine carries `updated_at`: pass it as `base_updated_at` to `edit_routine`, which refuses the edit if the routine changed in the Reps app after you read it.

get_routines