JustGains

Generate a real, road-and-path-snapped ROUTE (a plannable run / ride / walk / hike path) starting and ending at the user's location, and save it to their Routes tab. Use when the user asks you to build / make / plan a route, a running loop, a bike ride, etc. Use startLat/startLng from the app-data block's current location when present, or coordinates the user explicitly gives; NEVER guess them. If neither is available, OMIT startLat/startLng and the route starts from the user's last known training location (the start of their most recent GPS activity or saved route). Before calling, make sure you know the activity type and the distance they want (ask if they haven't said). The generated route follows actual streets and paths and lands close to the requested distance.

create_route

Get a workout program (template) by id, including its weeks and days. Use after search_workout_programs or get_my_workout_programs to dig into a specific program. Set includeData=false for a lightweight summary that omits per-day workout content.

get_workout_program

Remove foods the CURRENT user asks to delete from their diary, e.g. 'remove those crackers', 'I did not eat that', or 'delete breakfast'. Identify the exact saved entries from the user's request and the latest food result (log, removal or diary read); call get_my_food_diary for the relevant day only if no recent result has them. Pass their diaryEntryId and expectedUpdatedAt exactly as that result gives them. Remove only requested entries; ask which one if the target is ambiguous. For an entire meal, pass all entries in that meal, not the whole day. Removing one pack from a two-pack entry is a portion correction with log_my_food, not removal of the entire row. The API removes the batch atomically, updates day totals and syncs deletion to mobile. Repeating the same IDs is safe. This removes diary entries, never catalog foods. Do not call unless the user requested removal.

remove_my_food

Create a workout in the signed-in user's JustGains account, saved under their own creator profile. Provide a title and an ordered list of exercises (by code from search_exercises, or by name to auto-resolve); each exercise can include sets with reps/weight/RPE. Use this for precise, user-specified workouts (use generate_workout for AI-generated ones).

create_workout

Search the JustGains exercise library by name (optionally filtered by muscle group or equipment). Returns exercise codes and supported measurements to use when building or updating a workout.

search_exercises

Display a workout in the preview editor by its ID

show_workout

Update the CURRENT user's enrollment on a workout program. Use to start, abandon, or complete a program: 'start this program', 'I'm done with PPL', 'abandon the cut program'. Requires the program id (use search_workout_programs to find it). Action must be one of: start | abandon | complete. Note: 'start' uses the Purchasing status, matching the existing API behavior.

set_my_program_engagement

Patch the CURRENT user's profile. Only the fields you supply are changed. Top-level: bio, measurementSystem ('metric' | 'imperial'), userTimezone (IANA), autoStopAbandonedWorkoutsSeconds (0–86400). Private meta (under privateMeta.* keys): birthDate (ISO-8601), heightCm, gender ('Male'|'Female'|'MTF'|'FTM'), experienceLevel ('Beginner'|'Intermediate'|'Advanced'), fitnessGoals (string array). Use when the user asks to change any of these. Confirm before destructive replacements (e.g., overwriting fitnessGoals).

update_my_profile

Get the CURRENT user's bodyweight log (entries plus summary: current, lowest, highest). Use whenever the user asks about their bodyweight: 'what do I weigh now', 'how much have I lost', 'show my weight trend', 'when did I last weigh in', 'what was my lightest'. For ANY HISTORICAL TIMEFRAME ('what did I weigh in March', 'last summer', 'between Jan 1 and Feb 14'), pass `since` and/or `until` (ISO-8601). Summary stats (current/lowest/highest) are returned for BOTH the full history and, when a window is set, the windowed slice. Optional `limit` truncates the entry list. Requires sign-in.

get_my_weight_history

Read the CURRENT user's food diary, daily totals, targets, local date/timezone and last 30 days of foods (up to 100 entries). Call when the user wants to see their diary, when a request depends on a past day ('same as yesterday'), or to find entries to correct or remove that no recent food result returned. Routine logging does not need it: log_my_food resolves the local date and checks recent entries on the backend. Never infer that a planned meal was eaten.

get_my_food_diary

Get the CURRENT user's recorded history for a SINGLE exercise (by exerciseCode), plus their personal best. Use when the user asks 'show my bench press progression', 'how heavy have I squatted', 'what's my best deadlift', 'when did I last do pull-ups'. You usually want to call search_exercises FIRST to resolve a name to a code. For ANY HISTORICAL TIMEFRAME ('my bench in 2024', 'squats last summer'), pass `since` and/or `until` (ISO-8601). The tool sweeps deeper pages automatically and returns only sessions in the window: DO NOT page manually. Use `maxSessions` to cap the scan. Returns history items (workout id, completed-at, sets) sorted newest-first by default, plus a personalBest summary if any has been recorded. Requires sign-in.

get_my_exercise_history

Get the CURRENT user's workout-log history (workouts they actually performed and recorded). Use this whenever the user asks about THEIR OWN workouts - 'my last workout', 'what did I do this week', 'how much did I bench Monday', 'show my recent sessions', 'workouts in March', 'last summer's training'. For any historical timeframe, pass `since` and/or `until` (ISO-8601). The tool will paginate deeper automatically until the requested window is covered (or `maxLogs` is reached). For RANKED questions ('what was my best workout', 'longest session ever', 'highest-volume day'), set `rankBy` ('volume' | 'duration') and `topN`. The tool then sweeps the window, computes the metric per log, and returns the top N logs sorted by that metric instead of newest-first. Returns logs with id, title, date, exercise count, and a per-exercise summary of sets/reps/weight; when ranking, each log also carries totalVolumeKg/totalVolumeDisplay and durationSeconds. Returns an error if the user is not signed in.

get_my_workout_logs

Fetch the CURRENT user's full profile snapshot: name, email, bio, measurement system, timezone, plus private meta (age/birth date, height, gender, experience level, fitness goals, injury tracking, baseline weight). Use whenever the user asks 'what's my profile', 'how old am I', 'what's my height', 'what experience level am I set as', 'what goals do I have'. Pair with `update_my_profile` if they want to change any of these.

get_my_profile

Get the CURRENT user's workout-program enrollments and progress. Use whenever the user asks about programs they are following: 'what programs am I on', 'what's my next workout', 'how far through PPL am I', 'show my active programs'. Returns each enrolled program's title, engagement status, last completed day, remaining workouts, the next scheduled workout id (if any), and the program id. Errors if the user is not signed in.

get_my_workout_programs

Get the signed-in user's training progress (daily gains, workout volume, steps, active days) over a timeframe. Provide startDate/endDate (YYYY-MM-DD) or a trailing number of days. Defaults to the last 30 days. Requires the user to have connected their JustGains account.

get_progress

List the signed-in user's most recent workouts (title, date, duration, total volume, sets, reps, exercise count). Use to discuss recent training, consistency, and volume trends.

get_workout_history

Analyze the CURRENT user's workout consistency over a window: longest streak, current streak (today/yesterday inclusive), distinct training days, total logs, and average workouts per week. Use for 'how's my consistency', 'what's my streak', 'how often have I trained lately'. Default window 60 days, max 365. For HISTORICAL consistency questions ('how consistent was I in 2024'), pass `endDate` (ISO-8601), the window becomes (endDate: days, endDate). Current-streak only counts when the window ends today/yesterday.

analyze_my_consistency

Cross-exercise leaderboard for the CURRENT user. Use whenever the user asks about their TOP / MOST / HEAVIEST exercises across the board: 'what's my most used exercise', 'top 3 lifts', 'heaviest exercises', 'what do I lift the most'. Scans the user's workout logs (default 365 days, capped at `maxLogsScanned`) and returns three rankings in one call: byFrequency (session + set count), byMaxWeight (peak single-set weight), and byVolume (total tonnage). Each entry includes the exerciseCode + name so the agent can drill into a specific lift via get_my_exercise_history. For HISTORICAL questions ('most-used in 2024', 'top lifts last summer'), pass `since`/`until` (ISO-8601). Use `topN` to widen/narrow each list (default 5, max 25). Requires sign-in.

get_my_top_exercises

Bundle a one-call snapshot of the CURRENT user's recent training: count of workout logs in the last `days` (default 7), per-muscle-group recovery data, weight delta vs `days` ago, and the most recent log id. Use for "how was my week", "quick recap", "how am I doing". For HISTORICAL questions ('how was my week ending June 1, 2024'), pass `endDate` (ISO-8601), the window becomes (endDate - days, endDate) instead of anchoring to today. Saves the agent from chaining get_my_workout_logs + get_my_recovery_analytics + get_my_weight_history.

summarize_my_week