addCalendarEventAttendee
ChatGPTcapacity.By Kaizer
Kaizer is the workspace personal trainers use to program and follow up their clients. Connect your Kaizer trainer account to work on your roster from ChatGPT. What you can do: - Find a client and review their profile, current routine, training status and workout history. - Generate a new routine with AI, continue from an existing one, or edit a routine in plain language; then send it to the client. - Adjust one exercise's sets, reps, load or RIR, and look up weight suggestions from the client's 1RM. - Follow progress: training analytics, per-exercise progression, weight history and physical test results. - Manage reminders, client notes and training plans (planifications). Who it is for: personal trainers and gym staff with a Kaizer trainer account. Clients (athletes) cannot connect. Limitations: every action works on data inside your Kaizer account only. AI routine generation runs in the background and can take a minute; you can ask for the result later. Deleting or overwriting data (routines, plans) asks for your confirmation first. Kaizer does not give medical diagnosis or treatment.
capacity.ready_for_client with archive: false. Returns { status }: archived, restored, already_archived, or not_archived. Archived routines only appear in getClientRoutines when status: "archived" is passed.starts_at/ends_at are full timestamps, not days. Book clients in with attendee_ids (they must be the trainer's clients — resolve names with findClientByName first). Pass repeat_frequency + repeat_until to make it recurring: one event per occurrence up to repeat_until (inclusive), capped at 366. The response is the FIRST occurrence; the rest share its group_id. is_enrollable lets clients sign themselves up — without it the event is private, visible only to its attendees; capacity caps confirmed attendees. Inside a gym the agenda is curated by its admins — a coach gets a 403 here (but keeps booking people in with addCalendarEventAttendee).due_at. Use it when they ask to be reminded of something.{ match }, { ambiguous }, or { not_found }.{ match }, { ambiguous }, or { not_found }.{ match }, { ambiguous }, or { not_found }.status: "cancelled" so you can see who dropped out — count only the confirmed ones when reporting how full a class is.from/to, YYYY-MM-DD). Returns the metrics you list in metrics, or ALL of them when omitted — each with a plain-language description. Metrics: adherence, workouts_per_day, most_trained_exercises, total_volume, sets_per_muscle_group. For the whole roster use getTrainerMetrics; for one exercise's progression use getClientExerciseAnalytics.sender is client for the client's messages and trainer for the ones sent from the trainer's side. A conversation_id of null means there is no chat with this client yet — reading never opens one.tags (the trainer's own client-tag names).from/to). Metrics: estimated_weight (per-rep 1RM-style estimate — set rep, 1=1RM), volume and relative_strength (estimated weight ÷ current body weight) — one point per completed workout. Pass include_baseline: true to also get the last point before the range. Get exerciseId from getRoutineDetails or searchExercises.installment_id recordClientPayment needs. next_installment_due_date is what recordClientPayment takes as pay_ahead_due_date; null while the charge is paused or has no price. Quote amount_due_formatted, never amount_due; paid_amount_formatted is what was already paid toward an installment in parts, which it owes that much less._formatted fields, never the raw amounts — those are in minor units, whose exponent depends on the currency. amount_formatted is the price of one period; what the client owes right now is owed_amount_formatted (0 while nothing is overdue). due_date is the OLDEST unpaid period's. Clients with payments disabled are absent entirely.status explicitly includes "archived".body_composition; getClientDetails already has the current weight.status explicitly includes "archived".light: true returns sessions per week + exercise/container names only (~10× smaller); default returns the full breakdown with sets/reps/weights (identical exercises across weeks collapse to one entry; weekly differences expand into a weekly array). Sessions come back as either session_groups (replicated across every week — edit with the grouped tools using session_group_id + session_node_group_id) or ungrouped_sessions (one-off, single-week — edit with the *ForSingleSession variants using session_id + session_node_id). Each session's content is a nodes tree where section/circuit/super_set containers carry children; even in light mode containers include their session_node_group_id and session_node_id, so use those to target a container as a parent (never invent an id). whiteboard nodes carry trainer notes in plain_text — surface them alongside exercises when describing a session so the trainer. An empty nodes array means no exercises yet. Sessions the client already trained are marked (trained_weeks on a group, trained: true on a session): they are the client's history and read-only — no edit, AI or manual, changes them.from/to, YYYY-MM-DD): their events, which clients trained on which day, and the routines running out of programmed weeks in the range. Use include to ask for a single section when that's all you need. Events carry calendar_event_id — that's the id every other calendar tool takes. Ask for the bookings section to get who holds a spot in every session of the range at once, plus who waits in line for a full one; getCalendarEventAttendees answers for one event.tags (the trainer's own client-tag names; tag is the user handle). Same data as getClientDetails returns per client. Filter by tags with ids from listTags.from/to, YYYY-MM-DD; up to 730 days apart). Returns the metrics you list in metrics, or ALL of them when omitted — each with a plain-language description of what it measures. These cover the whole client roster, not a single client. Metrics: adherence, workouts_logged, total_clients, workouts_per_day, workouts_per_client, most_used_exercises, personal_records, time_saved.effort is read and answered in effort_scale (rir by default).searchExercises and getTrainerClients take tag ids, and this is the only place they come from. Each tag returns its id, name and type ("exercise", "training_plan_and_template" or "client") — only exercise tags work as an exercise filter and only client tags as a client filter.created = success; failed = tell the trainer; still_running = trainer can ask later. gym_experience: 1=beginner, 2=intermediate, 3=advanced. weeks is capped at 16 (the generator's limit) — for a longer program, generate a block of that length and tell the trainer to extend or regenerate it later. Inside a gym the programs are the gym's and only its admins can create one — a coach gets a 403, so don't offer.trained_weeks / trained in getRoutineDetails): those stay exactly as they were. Status values: created = success (the updated routine is returned inline); failed = tell the trainer it failed; still_running = trainer can ask later.created = success; failed = tell the trainer it failed; still_running = trainer can ask later. Client profile fields are auto-filled.tags to search the trainer's own labels — it takes tag ids, so call listTags first to resolve a label's name into its id. Use difficulty (array of "beginner", "intermediate" and/or "advanced") to match any of those levels; exercises that have not been graded are excluded whenever it is set. Each result returns its name, muscle groups, equipment, difficulty and tags.can_remind on getClientPayments first; remind_blocked_reason says why it would fail.ready_for_trainer) to client-visible (ready_for_client). Use this when the trainer wants to send a routine that was generated as a draft (auto_send=false). Returns { status: "sent" } on success, { status: "already_sent" } if the client already has it, or { status: "not_sendable" } (with the current routine_status) if the routine isn't a sendable draft yet — e.g. still generating, failed, or canceled. Every outcome also carries routine_name, client_id and client_first_name/client_last_name for confirmation display.group_id siblings. Inside a gym only its admins can reshape the agenda; a coach gets a 403.effort on nodes whose show_effort is false. effort is in the unit of the exercise's effort_scale: to prescribe RPE 8 on an exercise stored in RIR, either send effort_scale: "rpe" with effort: 8 (the body is read in the scale it declares and the stored values are converted) or send effort: 2.effort on nodes whose show_effort is false. effort is in the unit of the exercise's effort_scale; sending a different effort_scale converts the stored values and reads this body in the new scale. Exception: an exercise linked across weeks has one scale, so changing effort_scale also re-expresses every other week of that exercise in the new scale (same effort, new unit).status: "archived" archives the plan, its template routine and every client routine assigned from it; moving it back out of archived restores them. An archived plan can be neither assigned nor synced. Inside a gym the programs are the gym's and any of its staff (admin or coach) can edit them.Click any prompt to copy it.
Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/kaizer"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/kaizer)