Skip to main content
Glama
Sign In
Garmin MCP

Garmin MCP

by colincooperio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Heart rate (one day)

get_heart_rate
Read-onlyIdempotent

Retrieve daily heart-rate stats—resting, min, max, 7-day average, and hourly readings—or query a local time window for detailed ~2-minute readings.

Instructions

Heart rate for one day: resting, min, max, 7-day resting average, and hourly min/avg/max in local time. Give from/to (local HH:MM) to also get every ~2-minute reading in that window, e.g. overnight or around a workout. detail='full' returns Garmin's raw payload (every reading, large).

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the window, local HH:MM, inclusive. Defaults to 23:59 when only 'from' is given.
dateYesYYYY-MM-DD, or 'today' / 'yesterday' (resolved in the user's Garmin time zone).
fromNoStart of a full-resolution window, local HH:MM. Defaults to 00:00 when only 'to' is given.
detailNocompact (default) keeps the meaningful fields in readable units; full returns Garmin's raw payload.compact

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Start of a full-resolution window, local HH:MM. Defaults to 00:00 when only 'to' is given.",
+  "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "End of the window, local HH:MM, inclusive. Defaults to 23:59 when only 'from' is given.",
+  "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+  "type": "string"
+}
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful behavioral detail: local-time reporting, ~2-minute reading granularity when a window is supplied, and a size warning for full raw payloads.

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?

The description is three front-loaded sentences with no wasted wording. It states the main output first, then optional window behavior, then the full-detail warning.

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 simple read-only daily heart-rate tool with four parameters and no output schema, the description is complete enough. It lists the main return values and explains the optional high-resolution and raw-payload modes.

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?

Schema coverage is 100%, so the schema already documents parameter formats and defaults. The description still adds meaning by explaining that from/to produces every ~2-minute reading in that window and that detail='full' returns Garmin's raw payload, which is larger.

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?

The description names a specific resource and scope: heart rate for one day, with the exact metrics returned (resting, min, max, 7-day average, hourly min/avg/max). This is clearly distinguishable from sibling wellness tools such as get_hrv or get_stress.

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 gives clear usage context for the optional from/to window, including examples like overnight or around a workout, and warns that detail='full' is large. It does not explicitly compare against sibling alternatives, keeping it at 4 rather than 5.

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

Deploy Server

Other Tools