List planned workouts
list_planned_trainingsFind planned training workouts on the calendar over a date window — the location step before reading or editing an existing workout ("Marie's tempo session on Thursday"). COMPETITIONS ARE NOT IN THIS LIST: races are a separate resource, so this alone never answers "what is on her calendar". use get_calendar in planned mode for the whole palette, or read planned/competitions/ with nolio_api_read. Returns rows {id, name, date_start, athletes, group, sport, has_structured_workout, …} without the workout itself: read a candidate with get_planned_training before editing it. Narrow the window to the dates the user implies.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_planned_trainings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| group | No | Group id (grp_…) carrying this event, for a workout planned on a whole group you manage. Omit it for an individual event. Never together with `athlete`. | |
| limit | No | Max rows (the response carries has_more). | |
| athlete | No | Athlete id (usr_…) whose calendar carries this event, the same id you read it with. Omit it for your own events. Never together with `group`. | |
| date_to | No | Window end, YYYY-MM-DD (inclusive). | |
| date_from | No | Window start, YYYY-MM-DD (inclusive). | |
| recurrence | No | Filter by a recurrence id (rcr_...). | |
| time_in_zones | No | Add the planned seconds per intensity zone on every row. Off by default, the breakdown is heavy and a location step does not need it. |