garmin-owl

Overview Schema Source Related Servers Discussions Admin

get_training_zones

Read-only

Retrieve current Garmin heart-rate and cycling-power zone floor thresholds to establish today's training zone boundaries. Use activity data to see time spent in each zone.

Instructions

Get current configured Garmin heart-rate and cycling-power zone floor thresholds.

Use for today's zone boundaries; use get_activity for time spent in zones during an activity. Garmin keeps no history of max HR, LTHR or zone settings, so this cannot say what the zones were in the past: use get_activity or get_activities_detail, whose hr_zone_floors_bpm are the floors Garmin applied to each activity.

Requires saved local Garmin authentication (garmin-owl-auth). Reads Garmin and may update the local cache; never changes your Garmin account. Garmin failures are not retried automatically.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Default
`note`	No	Garmin-configured zone floors only; no missing ceilings are inferred.
`power`	No
`heart_rate`	No
`availability`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.3.1Oct 24, 2026

addedOutput schema / $defs

Added value: +{
+  "AvailabilityNotice": {
+    "properties": {
+      "field": {
+        "title": "Field",
+        "type": "string"
+      },
+      "message": {
+        "title": "Message",
+        "type": "string"
+      },
+      "status": {
+        "title": "Status",
+        "type": "string"
+      }
+    },
+    "required": [
+      "field",
+      "status",
+      "message"
+    ],
+    "title": "AvailabilityNotice",
+    "type": "object"
+  },
+  "HeartRateZoneProfile": {
+    "properties": {
+      "lactate_threshold_heart_rate_bpm": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Lactate Threshold Heart Rate Bpm"
+      },
+      "max_heart_rate_bpm": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Max Heart Rate Bpm"
+      },
+      "resting_heart_rate_bpm": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Resting Heart Rate Bpm"
+      },
+      "sport": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Sport"
+      },
+      "training_method": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Training Method"
+      },
+      "zone_floors_bpm": {
+        "additionalProperties": {
+          "type": "integer"
+        },
+        "title": "Zone Floors Bpm",
+        "type": "object"
+      }
+    },
+    "title": "HeartRateZoneProfile",
+    "type": "object"
+  },
+  "PowerZoneProfile": {
+    "properties": {
+      "functional_threshold_power_w": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Functional Threshold Power W"
+      },
+      "sport": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Sport"
+      },
+      "zone_floors_w": {
+        "additionalProperties": {
+          "type": "integer"
+        },
+        "title": "Zone Floors W",
+        "type": "object"
+      }
+    },
+    "title": "PowerZoneProfile",
+    "type": "object"
+  }
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "availability": {
+    "items": {
+      "$ref": "#/$defs/AvailabilityNotice"
+    },
+    "title": "Availability",
+    "type": "array"
+  },
+  "heart_rate": {
+    "items": {
+      "$ref": "#/$defs/HeartRateZoneProfile"
+    },
+    "title": "Heart Rate",
+    "type": "array"
+  },
+  "note": {
+    "default": "Garmin-configured zone floors only; no missing ceilings are inferred.",
+    "title": "Note",
+    "type": "string"
+  },
+  "power": {
+    "items": {
+      "$ref": "#/$defs/PowerZoneProfile"
+    },
+    "title": "Power",
+    "type": "array"
+  }
+}

changedOutput schema / title

Previous value: -"get_training_zonesDictOutput"New value: +"TrainingZones"

Addedv0.2.0Sep 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations by naming the auth prerequisite (saved local Garmin authentication), clarifying that although it reads Garmin it may update the local cache — a nuance the readOnlyHint alone would not convey — and stating that Garmin failures are not retried automatically. These are exactly the operational facts an agent needs before deciding to retry or to report a failure.

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?

Four short paragraphs in a deliberate order: what it returns, when to use it vs alternatives, why the historical exclusion exists, then auth/cache/failure behavior. Every sentence carries information not available in the structured fields; nothing is padded.

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?

With an output schema present, return values need no explanation, and the description covers the remaining gaps: temporal limits, sibling routing, authentication requirement, cache side effect, and failure semantics. An agent can call this correctly and interpret a failure without further context.

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

Parameters4/5

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

The schema has zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description does not need param detail here and correctly spends its space on scope and behavior instead.

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?

Names a specific verb and resource: 'Get current configured Garmin heart-rate and cycling-power zone floor thresholds.' The scope word 'current configured' immediately distinguishes it from historical zone data and from activity-based zone queries, which the next sentence reinforces with named siblings.

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

Usage Guidelines5/5

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

Explicitly routes the agent: this tool for today's boundaries, get_activity for time-in-zone during an activity, and get_activity/get_activities_detail for historical zones, with a pointer to the exact field (hr_zone_floors_bpm) that carries the past values. It even states why this tool cannot be used for the past (Garmin keeps no history of max HR/LTHR/zone settings), so the exclusion is justified rather than arbitrary.

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