Gyroscope

Gyroscope lift history for this member's Gyroscope account: the strength-training details logged in the app or through this connection (exercises, sets, weights, reps, time, notes and per-exercise e1RM benchmarks) between explicit start and end dates (YYYY-MM-DD), spanning up to 366 days, newest first. Optional exercise filters the sets to one exercise name or slug (substring match). Use it for "is my bench going up" questions and before suggesting loads.

load_strength_history

Gyroscope trend for this member's Gyroscope account: weekly or monthly aggregates of one metric (steps, sleep, calories, protein, weight, workouts, rhr, hrv) between explicit start and end dates (YYYY-MM-DD), spanning up to 366 days. Periods are ISO weeks (Monday start) or calendar months in the member's timezone, clipped to the range; a period with no samples is left out. Per period: sample count, average, min, max and total in the stated unit; weight adds first/last weigh-in, sleep adds the average sleep score, workouts add total calories (total = minutes, average = minutes per session). Use it for "how has my X changed" questions instead of many day reads.

load_trend

Gyroscope weather for this member's Gyroscope account on one or more explicit dates: the readings recorded where the member was (local time, temperature in C and F, summary, humidity, wind speed, UV index) and the day's high, low and most frequent summary. Dates must be ISO YYYY-MM-DD strings, no future dates. Maximum 31 days per call. No coordinates or place names.

load_weather

Gyroscope workout program state for this member's Gyroscope account, read-only: the current program state the app keeps, the quick-workout state and the saved setup answers (days per week, equipment, experience, goals, restrictions, session minutes and the like), as stored. The program library and the routing rules live in the app; the program is changed in the app, never through this connection. Parts are null (setup empty) when nothing is saved.

load_workout_state

Gyroscope workout, run, and bike summaries for this member's Gyroscope account on one or more explicit dates. Dates must be ISO YYYY-MM-DD strings, no future dates. Maximum 31 days per call. Returns named sessions and totals only, never raw high-frequency sensor streams.

load_workouts

Gyroscope food log for this member's Gyroscope account: log a prior food item again ("same as yesterday's breakfast"), copying its caption, nutrition and photo reference, as a new item at the given time. Need before calling: the item id from load_food for the day it was first logged (items with has_photo keep their photo). meal is only a morning/day/evening bucket, inferred from the time when omitted. Counted in the day's totals at once. Confirmed in one line. Deleting or editing is done in the app; this connection cannot delete.

log_again

Gyroscope bike ride for this member's Gyroscope account: log a manual ride (distance, start and end or duration) that no device tracked. Rides synced from a device or HealthKit appear in load_workouts, so a ride overlapping one there is already tracked. Need before calling: the start time and either the end time or the duration in minutes, from the member; do not guess missing times, ask for the one missing thing. Minimum before saving: start, duration or end, and distance; convert miles to km yourself. If anything is missing, ask short questions before calling. distance_km 0.01 to 1000; 1 minute to 10 hours. Additive, confirmed in one line. Deleting or editing is done in the app; this connection cannot delete.

save_bike

Gyroscope food log for this member's Gyroscope account: log a text-only consumed item from a direct member request. Use this for normal food items and meals, but also for anything the member consumed: water and other drinks; supplements, vitamins, powders, electrolytes, creatine, etc.; snacks, bites, desserts, sauces, alcohol/caffeine, or any other edible/drinkable item. "meal" is only a loose database bucket for morning/day/evening placement. It does NOT mean the item must be a literal meal: a glass of water, coffee, vitamin, protein powder, snack, or late-night bite still uses this tool. Exact time/structure is not critical. If the member does not name a bucket, leave meal out: Gyroscope files the item by the member's meal schedule (by default a late dinner until 1am counts for the day before, 1am to 4am is its own late-night bucket, breakfast from 4am, lunch from 11am, dinner from 5pm). Never pass latenight; Gyroscope assigns it. Do not tell the member water/drinks/supplements cannot be logged. They can be logged here as consumed items. Need before calling: the caption (what they consumed, including amount if given); if it is missing, ask "What should I write as the caption?". Preferred: estimate calories, protein_g, carbs_g and fat_g yourself from the caption and amount, pass all four with the call, and state the estimate to the member; the member does not have to supply them. Gyroscope keeps those macros, counts them in the day totals at once, and its own food analysis fills in the rest (fiber, sugar, micronutrients) later. If you cannot estimate, send the caption alone: Gyroscope analyzes it from the caption, as if the member typed it in the app. Keep the caption to what they consumed; the numbers go in their own fields, never in the caption. Deleting or editing logged items is done in the app; this connection cannot delete.

save_food

Gyroscope run for this member's Gyroscope account: log a manual run (distance, start and end or duration) that no device tracked. Runs synced from a watch or HealthKit appear in load_workouts, so a run overlapping one there is already tracked. Need before calling: the start time and either the end time or the duration in minutes, from the member; do not guess missing times, ask for the one missing thing. Minimum before saving: start, duration or end, and distance; convert miles to km yourself (1 mi = 1.609 km). If they say "half marathon" without a time you may set distance_km=21.0975 but MUST ask for the start and duration before saving. distance_km 0.01 to 1000; 1 minute to 10 hours. Additive, confirmed in one line. Deleting or editing is done in the app; this connection cannot delete.

save_run

Gyroscope workout for this member's Gyroscope account: create a NEW manual workout time block for a session no device tracked. Watch and HealthKit workouts sync on their own and appear in load_workouts, so a session overlapping one there is already tracked, and lifts for it go on with add_strength_training_details. Need before calling: the start time and either the end time or the duration in minutes, from the member; do not guess missing times, ask for the one missing thing. activity is the closest real type, e.g. "Traditional Strength Training", "Functional Strength Training", "HIIT", "Yoga", "Pilates", "Core Training", "Walking", "Hiking", "Swimming", "Tennis", "Other"; for runs use save_run and for rides save_bike. 1 minute to 10 hours; calories default to Gyroscope's estimate when omitted. Additive, confirmed in one line. Deleting or editing is done in the app; this connection cannot delete.

save_workout