Get training profile

What your assistant is told

Read the calling user's Fitness profile — goal, experience, training cadence, unit preference, plus any optional identity fields the user shared (sex, birth year, height) and their limitations note (injuries, joints to avoid, movement restrictions, in their own words). It also carries their **equipment by place**: equipment is the places they train ("Home", a named gym) and what they have at each. That is the specific answer; trainingContext is the one-word fallback for someone who never filled it in. An empty equipment means they have told us nothing yet, NOT that they own nothing — get_my_equipment and add_my_equipment are the tools that read and change it. It also carries **niggles: what currently hurts**, as the user told the app — read this before you program anything. Each one names a catalog safety tag the lifts you suggest should honour, how long it runs for, and the user's own note. A niggle is **the user's word, not a diagnosis**: they tapped "my knee" in a list, nobody examined anything, and you should neither name a condition nor treat one. An empty list means they have not told us anything hurts — not that nothing does. set_niggle and end_niggle change it, and suggest_substitution already reads it. Every field is optional and may be null. If the user hasn't onboarded yet the call still succeeds with all fields null so you can offer to fill them in.