ChatGPT Plugin

Simma

Triathlon & endurance coaching

Brand: Unknown

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Simma turns swimming, running and cycling data into coaching for triathletes and endurance athletes. It reads activities from Garmin, computes the numbers a triathlon coach actually uses — form calibrated to each athlete's own history, per-sport training status across swim, bike and run, pace and stroke detail down to the lap — and gives ChatGPT the finished picture rather than raw files. For coaches. Whether you coach triathletes, runners, cyclists or swimmers, ask who on your roster needs attention this week and why. Open one athlete and get three weeks of sessions bucketed by week, their load against their own baseline, race goals with days to go, the linked training plan, and pre-computed flags for the things worth a message. Draft that message in your own voice, save it, and send it from Simma so replies thread back into the same conversation. Keep private notes per athlete that steer every future draft. Every number is computed by Simma; ChatGPT writes the words. For athletes. Ask how your triathlon training is going and get an honest read against your own history, not a generic scale. Look up any swim, ride or run in detail, find the sessions where you faded or negative-split, set and track race goals, link a training plan, and message your coach — or, if you are self-coached, get the same analysis Simma gives a coach. What it does not do. Simma never sends anything on your behalf without an explicit confirmation step, and read tools are marked read-only so ChatGPT can use them freely. Tools that overwrite a setting, delete a goal or end a coaching relationship are marked destructive so ChatGPT asks before running them. Sending a message is gated twice: the draft is shown to you in full and must be approved before it goes. You need a Simma account; new users can create one during sign-in. Activity data comes from Garmin Connect, linked from the Simma web app. Your training history loads within a few minutes of linking, as long as historical data is allowed on Garmin's consent page.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-10-15
Tool count: 27
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Simma has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

27 tools agents can invoke

Report which safety gates are active for send_draft in this client. Run it before relying on send_draft: the strongest gate — asking the coach directly before each send — only exists if the client supports MCP elicitation, and the server cannot know that until a client connects. By default this reads what the client declared, which is a claim rather than proof. Pass `probe: true` to actually raise a throwaway confirmation prompt and find out whether it works. A client can advertise the capability and still fail to show anything, and only a probe catches that.
check_send_safety
Add a goal for the athlete: an event with a date and one target per discipline. A goal with one target takes that discipline; more than one makes it a multi-discipline goal. Each target needs a distance or a time. Confirm with the coach before calling this.
create_goal
Remove a goal permanently. Prefer update_goal with status `completed` or `archived` when the goal happened or was abandoned — that keeps the history the context builder reads. Delete only for mistakes, and confirm with the coach first.
delete_goal
Delete a draft that was never sent. Use it to clear a draft the coach decided against, or one you created and no longer need — otherwise it stays in the thread indefinitely. Drafts only. A message that has been sent cannot be deleted, and should not be: removing it would not unsend the email, but it would break the routing that delivers the athlete's reply back into the thread and erase the record of what was actually said.
discard_draft
Every session in a window with its pacing shape, plus a roll-up. Answers questions like "which swims faded in the main set this month" or "is she negative-splitting more often" from summaries Simma computed when each activity was saved — no lap data is read or averaged here. Two views per session. `mainSet` is the longest segment (a swim's main set, the ride itself) and is what a coach means by "did they fade". `session` is every lap including warm-up and cool-down, so a structured swim often reads faded there while the main set was even or negative. Prefer mainSet; mention session only when the two disagree and it matters. Shapes: negative_split (back half faster by >2%), even (within -2..+3%), faded (+3..8%), faded_hard (>8%). fadePercent is positive when they slowed. paceVariationPercent is lap-to-lap consistency. `lapSource: splits` means the laps were derived from the pace series at the stated distance because no lap button was pressed — say so if you quote a lap number. Sessions with too few laps to judge are listed with shape null so you can see they existed; do not read anything into them. `structure: opening_burst` or `two_paced` means the set had two regimes — sprints then steady, or fast/easy alternating — and the shape was judged on the steady block; `rawShape` is what a naive whole-set split would say. Do not describe a two-paced set as fading. `lapsExcludedAsDeviceErrors` counts laps faster than physically possible that were set aside before judging: a miscounting watch, not an athlete.
find_sessions_by_shape
Full detail for one activity, including every lap and the split structure. Large series (GPS traces, heart-rate and pace graphs, elevation profiles, stroke analytics) are summarised rather than inlined. Use this to discuss a specific session. Values are metric. The document carries an imperial copy of each display tile, which is dropped here because it is the same data converted — it was a third of a ride's payload. Check the coach's or athlete's preferredUnits (get_coach_profile, get_athlete_profile) and convert when speaking to someone who uses imperial; do not report kilometres to a coach who works in miles.
get_activity_detail
The richest single view of an athlete, and the right starting point before writing anything to them. Returns three weeks of activity bucketed by week with per-sport volume, training load with 7-day deltas and trend, per-sport training status, goals with days-to-event, the linked training plan, and pre-computed notable flags. Every number here was computed by Simma against this athlete's own history. Treat the flags and figures as established fact: do not re-derive averages, recompute percentages, or second-guess a severity. A flag carries a machine name, a severity, the sentence a coach would say, and the values behind it — and sometimes a context line that changes the reading entirely, such as a load spike that is a return from a break rather than overreaching. Read the context line before characterising a flag. Prefer this over assembling your own picture from list_athlete_activities.
get_athlete_context
Sleep, HRV, resting heart rate and stress for one athlete. Daily physiology from the athlete's Garmin watch: nightly HRV, sleep (duration, stages, Garmin's sleep score), resting heart rate and all-day stress, one row per calendar date, plus a summary that compares the last 7 days with the athlete's own window. Read `coverage` first: it says how many nights actually carry a reading, and a watch not worn to bed produces nothing. The readings are measurements against the person's own recent days, not medical findings; report them as such and do not diagnose. Garmin's Health API reaches back about 30 days, so the window is capped there in practice.
get_athlete_physiology
One athlete's profile and coaching relationship: name, contact, preferred units, pool length, self-rated ability by sport, and threshold values (swim/run pace, cycling power) that Simma's load model scores against. Also returns any linked Google training plan and a summary of the last 12 weeks of activities. Use this for who the athlete is; use get_training_status for how they are going.
get_athlete_profile
Aggregate statistics and training form for one athlete over a window, including fitness/fatigue/form history and active goals. Use for trends over weeks rather than individual sessions.
get_athlete_stats
Every athlete conversation with at least one message, most recent first, with the last message and unread count for each. Answers "who is waiting on me" across the whole roster in one call, rather than get_messages per athlete.
get_coach_inbox
Recent coach/athlete message thread, newest first. Useful for what has already been said before drafting anything new.
get_messages
The signed-in coach's own record: name, business name, public slug, invite code, and the voice settings Simma applies when drafting athlete emails (tone of voice, coaching instructions, sign-off). Read these before helping write anything so the wording matches what Simma itself would send.
get_coach_profile
Per-sport training status for one athlete: form score and zone, trend, detected pattern, days since last activity, session count and flags. This is Simma's own training-load model — prefer it over inferring load from raw activities.
get_training_status
How to sign this assistant out of Simma, or switch to a different Simma account. Nothing is changed by calling this; it returns the steps and a sign-out link. Use it when the person asks to log out, disconnect, or sign in as someone else.
get_sign_out_instructions
Attach a Google Docs or Sheets URL as the athlete's training plan. Simma reads it (read-only) when building coaching context, so plan-versus-actual comparison becomes possible. The document must first be shared with Simma's service account; if it is not, this returns the address to share it with — relay that to the coach rather than retrying. Replaces any plan already linked.
link_training_plan
List an athlete's activities, newest first, trimmed to summary fields. Prefer a date window (weeks/months/days) over paging. Use get_activity_detail for the full breakdown of a single session.
list_athlete_activities
An athlete's goals — event name, discipline, date, days until event, target time and notes. Use alongside training status to judge whether load suits the time to race.
list_athlete_goals
List the coach's athletes with their current training status, last activity, active goals and unread message count. Start here — it returns the athleteId needed by every other tool. Includes a per-athlete status such as overreaching, monitor, disengaged, quiet, welcome-back or recovering. Quiet means past their own usual gap between sessions with nothing this week — due, not yet disengaged. Paged: returns up to `limit` athletes (default 50) and a `nextCursor` when there are more. Pass it back as `cursor` to continue; a page can be shorter than the limit and still carry a cursor, so keep going until `nextCursor` is absent. Most rosters fit in one page.
list_athletes
End the coaching relationship with an athlete. They keep every activity and goal and land on Simma's house coach account; what goes is this coach's access to their training, the coach's private notes on them, and any training plan linked for them. The message thread stays stored but is no longer reachable from this roster. Cannot be undone from here: the athlete would need to join again with the coach's invite code. Get the coach's explicit agreement naming the athlete first; where the client supports it the coach is also asked directly and the call stops if they decline. Never remove several athletes from one approval.
remove_athlete
Store a message you have written to an athlete as a draft. Nothing is sent — the draft appears in Simma where the coach can read, edit and send it, and it is what send_draft takes. Read get_coach_profile first: the coach's tone of voice, coaching instructions and sign-off are what Simma itself writes with, and a draft that ignores them will not sound like them. Ground the content in get_athlete_context rather than in your own reading of the raw numbers. Returns the stored draft including the `sk` that send_draft needs.
save_draft
Send a saved draft to the athlete as a real email, immediately. This cannot be undone or recalled, and it arrives under the coach's name — the athlete has no way to tell it was written with an assistant. Show the coach the exact subject and body and get their explicit agreement before calling. Do not send on a vague instruction, and never batch sends across several athletes from a single approval. Where the client supports it, the coach is also asked to confirm directly and the send stops if they decline. `confirmSubject` and `confirmBody` must match the stored draft exactly, so a stale or mistaken `sk` cannot send a different message than the one that was approved. Take all three values from save_draft or get_messages rather than from memory.
send_draft
Detach the linked Google Doc or Sheet. Simma stops reading it; the document itself is untouched. Confirm with the coach first.
unlink_training_plan
Edit one of the athlete's goals: rename it, move the date, change the discipline or targets, add notes, or mark it completed or archived. Only the fields you pass change. Read list_athlete_goals first for the goalId and the current values, and confirm the change with the coach before calling this — it writes straight to the athlete's record. `targets` replaces the whole list, so include every target you want to keep. Distances are metres as a string; times are H:MM:SS.
update_goal
Set an athlete's thresholds, ability levels, units, pool length, name, body mass or date of birth. Only the fields you pass change. Thresholds are what every training-load number is scored against, so a wrong one reshapes the athlete's whole history: read get_athlete_profile first, state the old and new value to the coach, and confirm before calling this. Units are the ones a coach speaks in — pace as M:SS, speed in km/h — and are converted to what Simma stores. Cycling threshold power comes from a power meter (95% of best 20-minute power is the usual estimate); threshold speed is the fallback for riders without one and is the whole basis of their load, so set it with care. Body mass only affects the climbing term of the speed-based cycling estimate; it is safe to ask the athlete for. `ftpLocked` stops Simma's own auto-estimation from overwriting a threshold the coach has set deliberately. Birthdate is worth asking for: without it every heart-rate zone is derived from a default age of 40. It changes zones on activities processed from now on, not ones already stored.
update_athlete_profile
Set the coach's private notes on an athlete, or the specialty the coach works with them on. Notes are the coach's own memory of the athlete — training background, constraints, what they respond to — and are included in get_athlete_context, so what you write here shapes future drafts. `notes` replaces the whole text: read get_athlete_profile first and carry forward what should stay.
update_athlete_notes
Edit the signed-in coach's own profile: business name, public slug, and the voice settings Simma applies when drafting athlete emails (tone of voice, coaching instructions, sign-off). Only the fields you pass change; pass at least one. Read get_coach_profile first for the current values and confirm the change with the coach before calling this — the voice settings shape every draft Simma writes for them from then on. `signOff` is rendered verbatim at the end of each email; use a newline to separate the closing phrase from the name. The slug must be unique across coaches — a 409 means it is already taken.
update_coach_profile

FAQs

Simma ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Simma's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.