Skip to main content
Glama

Enroll in a catalog training plan

enroll_training_plan
DestructiveIdempotent

Enroll an athlete in an existing catalog training plan, once the athlete has confirmed the plan and start date. Side effects: every workout is scheduled on the athlete's calendar from start_date, the plan becomes their primary plan, a Garmin workout sync is queued when the athlete has Garmin connected, and when a coach enrolls an athlete the athlete gets an in-app notification. Repeating it changes nothing: an existing enrollment returns its plan_instance_id with already_enrolled=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "athlete_id": "<athlete_id>",
      "training_plan_id": "<training_plan_id>",
      "start_date": "<start_date>"
    },
    "name": "enroll_training_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
athlete_idYesThe athlete's user id: get_current_user's athlete_id for the connected account, or an id from get_coach_athletes or find_athlete.
start_dateYesFirst day of the plan, YYYY-MM-DD.
training_plan_idYesA catalog training_plan_id from recommend_training_plans.
long_run_preferenceNoLong-run day; omit to keep the plan's own long-run day.
training_days_per_weekNoTraining days per week, 2-7.

Output Schema

NameRequiredDescriptionDefault
errorNo
statusNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
warningsNo
next_stepNoWhat can be done next, for example after a failure.
athlete_idNo
start_dateNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
user_contentNoFields in this result that people wrote.
weeks_returnedNo
already_enrolledNo
plan_instance_idNo
training_plan_idNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it enumerates the calendar scheduling of every workout, promotion to primary plan, queued Garmin sync, and the coach-enrollment in-app notification. It also explains the repeat-call behavior precisely (returns plan_instance_id with already_enrolled=true), which makes the idempotency hint actionable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and its prerequisite, followed by a compact side-effects list and an idempotency clause. Every clause carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, multi-side-effect enrollment tool with five parameters, the description covers the trigger condition, all consequential effects, and repeat-call semantics. An output schema exists, so return-value documentation is unnecessary, and the already_enrolled flag is still surfaced where it matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with athlete_id sources, date format, and the long-run/training-days defaults all documented in the schema itself. The description only references start_date as the scheduling anchor and adds no new meaning to training_plan_id, long_run_preference, or training_days_per_week, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Enroll an athlete in an existing catalog training plan" gives a specific verb (enroll), resource (training plan), and scope (existing catalog plan), which separates it from create_training_plan and recommend_training_plans without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a real precondition: enrollment happens only after the athlete has confirmed the plan and start date. It does not name an alternative tool or a when-not-to-use case, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources