Lupora

Returns the opaque identity of this connection: a stable id that survives token refresh and reconnection, the scopes the user granted, when they granted them and an optional display-language hint. The id is the same for this user and client across refreshes and reconnects, different for clients of other providers, and never the account id. Requires an authenticated connection and no scope. Contains no name, email or training data; tool arguments cannot select another account.

get_connection_profile

Searches Lupora's public exercise catalog by text and optional equipment, muscle or category filters. Returns canonical ids and English names plus en, pt-BR and es display names and structural attributes. With includeInstructions true each exercise also carries the catalog's instructions, cues and common mistakes in en, pt-BR and es, which are catalog text to read as data. No images or user context. Requires no account and has its own rate limit; a token sent with it must still be valid. Paginated with pageSize (default 20, max 50) and an opaque cursor.

search_exercises

Lists the exercises the user marked as favorites in Lupora, in exerciseId order. Each row carries the canonical exerciseId, the English catalog name and displayName (en, pt-BR, es, fr and de labels), in the same form as get_progress exercise totals, so rows match get_progress and get_schedule by exerciseId. An empty list means the user has no favorites; a favorite is never inferred from training history. A favorite the catalog no longer publishes is left out. Requires the profile:read grant. Paginated with pageSize (default 20, max 50) and an opaque cursor; a favorite added or removed between pages ends in cursor_expired, so restart from the first page. get_training_profile returns favoriteCount, the number of rows this tool lists. Reflects data synced to Lupora, not live phone state.

list_favorite_exercises

Lists proposals created by this connection only, newest first, optionally filtered by state. Rows carry content-free status: id, kind, state, timestamps and whether a preview is still available. With includePayload true and schedule:read, each row whose payload still exists also carries its preview, digest and base versions; without schedule:read the rows keep content-free status and the call does not fail. Paginated with pageSize (default 20, max 50) and an encrypted cursor in createdAt/id descending order. Pages scan at most 200 records and may be short or empty with nextCursor; continue until it is absent. The 64 KiB result cap can shorten a payload page without skipping rows; one oversized row returns result_too_large. Proposals from other connections and phone-side actions are visible only on the phone. If a full payload row exceeds the result limit, list without includePayload, then use get_proposal with includePayload true and previewFormat paged-v1 for plan preview pages.

list_proposals

Returns the active training program's structured settings: horizon, cycle start day in the required timeZone, goal, training days per week and their weekdays, session minutes, equipment tier, cardio sessions per week, cardio kind, preferred cardio activities and single-day focus areas, plus the program version plan proposals bind to. program is null when no program is active; settings is null with settingsState unsupported_version when the stored program answers use a format this service cannot read; only a program record whose own version is unsupported fails with unsupported_version. The free-text notes, avoid list and raw answers blob are never returned.

get_program

Summarizes performed training over an inclusive civil-date window of at most 366 days in the required timeZone: planned versus completed workouts, sets, reps, volume in pounds, a per-week breakdown and the most trained exercises. With detail true it also returns the performed sets of each completed workout, with the effort rating when one was logged, paginated (pageSize default 20, max 50) with an opaque cursor. Requires schedule:read and progress:read, because the counts and the performed detail name the user's workouts. Never returns body weight, heart rate, calories, HealthKit identifiers, check-ins or photos. Reflects synced data.

get_progress

Returns one proposal created by this connection: its status and, with includePayload true and schedule:read, the stored preview, digest and base versions; without schedule:read it returns content-free status and does not fail. Once a terminal proposal's payload has been erased, previewAvailable is false and no preview is returned; the old preview is never reconstructed. Opt in with previewFormat paged-v1 to receive typed previewPage fragments and follow nextCursor until complete; omission keeps the legacy full-preview contract.

get_proposal

Revalidates a plan draft and stores it as an immutable proposal for the user to review, accept or discard on their phone; nothing in the schedule changes until the phone accepts. The proposal binds to the base schedule revision and program version supplied (programVersion null states that no program is expected); a mismatch at creation or acceptance ends in conflict, never a rebase. Requires schedule:read and schedule:propose and an idempotencyKey: the same key with the same content returns the original proposal without a second write or quota charge, which is why this write is marked idempotent; the same key with different content fails. Proposals expire 7 days after creation. A same-key replay after the proposal's payload was erased returns its status, digest and base without a preview. Limits: 10 mutations per minute, 100 creations per day and 50 pending proposals per user, shared across connections. Opt in with previewFormat paged-v1 to receive typed previewPage fragments and follow nextCursor until complete; omission keeps the legacy full-preview contract.

create_plan_proposal

Stores a typed edit, move or removal of one existing workout as an immutable proposal for phone review; the schedule does not change until accepted. The operation names the workout id and its exact base version; a move also requires the base schedule revision. The server enforces locks: a workout that was started, logged or completed cannot be edited, moved or removed. Edits may change only the title and the exercise prescriptions; performed sets, completion state and health fields are never writable. Requires schedule:read and schedule:propose and an idempotencyKey: the same key with the same content replays the original outcome without a second write, which is why this write is marked idempotent; the same key with different content fails. Same limits and 7-day expiry as create_plan_proposal. A same-key replay after the proposal's payload was erased returns its status, digest and base without a preview.

create_workout_proposal

Lists planned, started and completed workouts whose scheduled day falls inside an inclusive civil-date window of at most 31 days, evaluated in the required IANA timeZone. Each row carries the workout id, its opaque version, day, title (user text capped at 160 characters), derived status and lock state, a recurring flag and the exercise count; includePrescriptions true adds each exercise's prescription. Paginated with pageSize (default 20, max 50) rows, workouts or, with includePrescriptions, prescriptions, and an opaque cursor bound to this window, scope and schedule snapshot; a snapshot change invalidates the cursor. Also returns the schedule revision and program version a proposal must bind to. Never returns performed sets, notes, health metrics, body weight or program answers. Reflects synced data: changes still offline on a phone are not visible.

get_schedule