UltraFit360

Assign an EXISTING pre-made program template from the UltraFit360 catalog. WORKFLOW: 1. Call list_programs to find the template_id 2. Call get_current_program so you can name the program being replaced 3. Show the user the new program, and state the exact impact: their current program (name it) is deactivated and unstarted sessions are removed. Logged workout history is never deleted. If they have no active program, say that instead of warning about a replacement. 4. Wait for explicit user approval ('yes', 'do it', 'save it', etc.) 5. ONLY THEN call assign_program({template_id}) IMPORTANT: Do NOT call this tool immediately after finding a template. First present the program to the user in natural language and wait for explicit approval. WHEN TO USE: Only for existing catalog templates. For custom splits or bespoke routines, use create_custom_program instead.

Build a custom workout program from scratch. WORKFLOW: 1. Call list_exercises({"compact": true}) to load the full exercise catalog 2. Call get_current_program to see what they train now, so you can name the program being replaced and carry over anything worth keeping 3. Design the program and show it in full — days, exercises, sets and reps 4. State the exact impact: their current program (name it) is deactivated and unstarted sessions are removed. Logged workout history is never deleted. If they have no active program, say that instead of warning about a replacement. 5. Wait for explicit user approval ('yes', 'do it', 'save it', etc.) 6. ONLY THEN call create_custom_program with the program details IMPORTANT: Never call this tool immediately after designing a program. First show the complete program to the user in natural language and wait for approval. USAGE: Build custom programs when no catalog template fits (list_programs) or for bespoke designs (5-day PPL, aesthetic V-taper, etc). The program becomes the user's active program immediately but is NOT added to shared templates — verify with get_current_program, not list_programs.

Create planned meal OPTIONS in the user's UltraFit360 meal plan — applied immediately in a single call. The app shows several options per meal type, so send one entry per meal (you can include multiple breakfast options, etc.). By default, sending new options for a meal_type REPLACES that meal_type's current options (other meal types are untouched); set append=true to add options without replacing. Only the newest few options per meal_type stay active. Check get_progress_overview / coaching memory for the user's calorie & macro targets first.

Get the user's logged body metrics over time — body weight, body-fat %, and other measurements — keyed by date, from UltraFit360. USE THIS for questions about weight trend, how much they weigh, whether they are gaining or losing, or any body-composition change over time. Examples: 'how has my weight changed this month?' -> {"days": 30}; 'what did I weigh on/around June 1?' -> {"start_date": "2026-06-01", "end_date": "2026-06-08"}.

Get the user's AI coaching memory — a structured summary of their profile (age, height, current weight, activity level), active goal (e.g. weight gain/loss + target), current program, training/nutrition context, lifestyle notes, and coach notes. USE THIS to learn who the user is and what they are working toward before giving advice, or when they ask about their goal, target weight, or current plan. Takes no time window. Example: 'what's my current goal and program?' -> {}.

Get the user's currently assigned workout program — its days and the exercises in each day, including each exercise's user_exercise_id (needed to replace it) and its catalog number `n` (reusable in create_custom_program). USE THIS before editing a workout so you know what's there. Returns empty days if no active program. The id fields (user_exercise_id, n, *_program_id) are internal — use them in tool calls but NEVER show or mention raw ids or numbers to the user; refer to exercises by name.

Get the user's logged meals and per-day nutrition totals (calories, protein, carbs, fat) from their UltraFit360 food diary, aggregated by date. USE THIS whenever the user asks what they ate, their food/meal history, calorie intake, macros, or how their diet looked over any period. This is the single source of truth for their nutrition — do not answer such questions from memory. Returns an empty list if nothing was logged in the window. Examples: 'what did I eat this week?' -> {"days": 7}; 'show my macros from June 1 to June 8' -> {"start_date": "2026-06-01", "end_date": "2026-06-08"}.

Get a single composite snapshot combining nutrition, body metrics, workouts, AND coaching memory for the window — the most efficient call when the user wants a broad progress update. USE THIS for 'how am I doing?', 'give me a progress report/summary', or any question that spans diet + weight + training together, instead of calling the individual tools separately. Examples: 'how's my progress this week?' -> {"days": 7}; 'summarize my last month' -> {"days": 30}.

Get the user's completed workout sessions in the window plus their all-time personal bests (max weight per exercise) from UltraFit360. USE THIS for questions about training history, what workouts they did, how often they trained, or their strength PRs. Returns session_count=0 when nothing is logged. Examples: 'what workouts did I do this week?' -> {"days": 7}; 'show my training in the first week of June' -> {"start_date": "2026-06-01", "end_date": "2026-06-08"}.

Load exercises from the UltraFit360 catalog. WHEN BUILDING A CUSTOM PROGRAM: Call list_exercises({"compact": true}) ONCE at the start. It returns the curated catalog (~725 proven exercises covering every muscle x equipment combination), each as {n, short_name, muscle}. `n` is the exercise's permanent catalog number — pass it as exercise_id in create_custom_program / replace_exercise. Pick ONLY numbers from the returned list; never invent them. FOR ANYTHING NOT IN THE CURATED LIST, OR QUICK LOOKUPS: Use filters over the full ~1,500-exercise catalog: {"muscle": "chest"}, {"equipment": "barbell"}, {"name": "Bench Press"}. Filtered results also carry `n`. IMPORTANT: Use `n` in tool calls, but refer to exercises by name in conversation — never show raw numbers or ids to the user.