Skip to main content
Glama

getDailyHeartRate

Read-only

Retrieve a day's Garmin heart rate data for a specified date, including resting, min, max, seven-day resting average, and timestamped bpm samples to plot the day's HR curve.

Instructions

Heart rate of one day, yyyy-MM-dd: restingHeartRate, minHeartRate and maxHeartRate (bpm), lastSevenDaysAvgRestingHeartRate, and heartRateValues, the samples of the day as [timestamp, bpm] pairs (several hundred, so the answer is about 13 KB). Use it for the HR curve of a day. For resting HR over several days use getDailySummary with fromDate and toDate; for the zone limits use getHeartRateZones.

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": {
      "date": "<date>"
    },
    "name": "getDailyHeartRate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate yyyy-MM-dd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description focuses on what annotations can't convey: the response shape and its size (~13 KB, several hundred [timestamp, bpm] pairs). That payload-size warning is genuinely useful for planning. It stops short of noting edge cases such as missing data for a date or timezone handling for the timestamps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource and the day scope, then the field list, then the alternative routing. The dense field enumeration is information the agent needs, though the nested 'heartRateValues ... (several hundred, so the answer is about 13 KB)' clause is slightly tangled and could read more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: named scalar fields plus the sample-pair structure and volume. Only minor gaps remain (empty-day behavior, timestamp units/timezone), which are not fatal for a single-read tool.

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

Parameters3/5

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

Schema coverage is 100% and the single 'date' parameter is already documented as yyyy-MM-dd. The description repeats the format but adds no syntax, range, or boundary meaning beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb+resource (heart rate of one day) and enumerates the exact returned fields (restingHeartRate, min/max, lastSevenDaysAvgRestingHeartRate, heartRateValues). It explicitly distinguishes itself from getDailySummary and getHeartRateZones, so an agent can pick it without opening any schema.

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?

Gives a positive selection rule ('Use it for the HR curve of a day') and names two concrete alternatives with their triggering conditions: getDailySummary with fromDate/toDate for multi-day resting HR, getHeartRateZones for zone limits. Nothing is left implicit.

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