Propose a plan revision
propose_plan_revisionPropose a changeset of several workouts or weeks against one training plan, for example rebuilding a week or shifting a block. For a single workout whose load should change, propose_workout_adjustment fits. Nothing changes until approve_plan_revision applies it; group changes then reach every member.
scope='athlete' (plan_instance_id + athlete_id) — each operation is one of:
{op:'adjust', workout_id, changes:{...}} — changes allows: workout_name, status ('scheduled' or 'skipped' only), workout_type, workout_sub_type, day, target_distance_in_meters, target_duration_in_seconds, target_pace, target_pace_zone, target_complete_date, content_blocks. Applied like a calendar edit: a new target_complete_date moves the session and its week.
{op:'add', workout:{...}, target_complete_date} — workout requires workout_name and allows: workout_type, workout_sub_type, day, target_distance_in_meters, target_duration_in_seconds, target_pace, target_pace_zone, content_blocks. target_complete_date sits at the OPERATION level, not inside workout.
{op:'remove', workout_id}
scope='group' (plan_instance_id = group plan instance id; coach role and the group-training-plan feature required) also supports {op:'reschedule', workout_id, new_week, new_day}; group add requires workout_name, week (or week_number), day inside workout. Group adjust changes allows: workout_name, workout_description, workout_description_cards, workout_type, workout_sub_type, target_distance_in_meters, target_duration_in_seconds, content_blocks, session, is_group_workout, group_content, target_pace_zone, target_pace, day, attendance_enabled, attendance_rule, live_session_enabled, entry_kind, icon, clear_content_blocks (other keys are rejected).
Strength sessions: a strength workout with a structured session (sets, exercises, loads) derives its duration from that session and cannot carry content_blocks; to change its volume, edit the session in the workout editor (athlete adjust rejects a different target_duration_in_seconds). Changing workout_type away from strength drops the session.
Rules: target_complete_date is an epoch-SECONDS integer (milliseconds are accepted and auto-converted). An athlete workout does not accept week or status: week is derived from target_complete_date and status is system-managed. Completed workouts cannot be adjusted, moved or removed. An athlete with a coach may propose, but their coach approves. Re-proposing an already applied changeset is refused, and re-proposing a pending one returns the same revision. Example athlete add: {op:'add', workout:{workout_name:'Easy Run', workout_type:'run', target_distance_in_meters:6000, target_pace_zone:'Z1'}, target_complete_date:1781568000}. Workout reads return content_blocks as rows whose columns content_block_fields names (an interval's blocks column holds its nested steps as rows in the same columns), and a session shared by several rows as session_ref into session_definitions. As arguments, content_blocks is a list of block objects and session a session object.
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": {
"scope": "<scope>",
"plan_instance_id": "<plan_instance_id>",
"operations": "<operations>",
"reason": "<reason>"
},
"name": "propose_plan_revision"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Optional notes for the reviewer. | |
| scope | Yes | athlete: one athlete's plan; group: a group plan. | |
| reason | Yes | Why the plan changes; the reviewer reads it. | |
| athlete_id | No | The athlete whose plan changes; athlete scope only. | |
| operations | Yes | The changes, applied in order on approval (1-50). | |
| plan_instance_id | Yes | athlete scope: plan_instance_id from get_training_plan or get_week_workouts; group scope: group_plan_instance_id from list_group_plans. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| kind | No | ||
| error | No | ||
| notes | No | ||
| scope | No | ||
| org_id | No | ||
| reason | No | ||
| source | No | ||
| status | No | ||
| message | No | ||
| privacy | No | Present when the athlete's settings withhold data. | |
| coach_id | No | ||
| warnings | No | ||
| next_step | No | What can be done next, for example after a failure. | |
| applied_at | No | ||
| athlete_id | No | ||
| created_at | No | Epoch milliseconds. | |
| operations | No | ||
| updated_at | No | ||
| apply_error | No | ||
| next_cursor | No | Reads the next page; null on the last page. | |
| reason_code | No | ||
| reviewed_at | No | ||
| revision_id | No | ||
| total_weeks | No | ||
| user_content | No | Fields in this result that people wrote. | |
| applied_at_iso | No | The epoch field beside it as a UTC instant; the local day can differ. | |
| coach_feedback | No | ||
| created_at_iso | No | The epoch field beside it as a UTC instant; the local day can differ. | |
| updated_at_iso | No | The epoch field beside it as a UTC instant; the local day can differ. | |
| weeks_returned | No | ||
| reviewed_at_iso | No | The epoch field beside it as a UTC instant; the local day can differ. | |
| plan_instance_id | No | ||
| truncated_fields | No | Lists cut to fit one response: rows returned and total. | |
| generated_content | No | Fields in this result that NexRex's AI wrote. | |
| operation_results | No | ||
| session_definitions | No | Sessions that several rows of this result share by session_ref. | |
| content_block_fields | No | Column names of every content_blocks row, nested blocks rows included. |