zone_by_gait
Splits heart-rate zone time by gait—running, walking, standing—using each activity’s own boundaries, so zone-2 minutes are reported per run or local ISO week without mixing gait types.
Instructions
M7 time in HR zone split by GAIT — running vs walking vs standing.
Zone-2 minutes are the headline, per run and rolled up per LOCAL ISO week.
WHY THE SPLIT MATTERS: a pooled zone-2 total mixes a walk up a climb
with running on the flat, and those are different training. On a hilly
run/walk session the walking share of zone 2 can exceed the running share
— invisible in the pooled figure, and the whole point of the run/walk
structure.
Boundaries come from EACH ACTIVITY'S OWN FILE where present (§14e); a
corpus spanning zone changes holds several distinct sets, and
`boundary_set` says which ruler a
run was measured with, and a week spanning two is reported as SPLIT rather
than summed into a number that is on no scale.
Do not compare this against Garmin's hrTimeInZone: ours excludes stops and
flagged records and applies the 40 s HR lag, so it reads lower by design.
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": "zone_by_gait"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| last_n | No | ||
| cluster | No | ||
| end_date | No | ||
| run_type | No | ||
| direction | No | ||
| segment_id | No | ||
| start_date | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |