Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_heart_rate

Read-only

Read heart rate for a chosen day, including resting rate, 7-day average, min/max, hourly stats, and optional raw samples.

Instructions

Heart rate for one day: resting heart rate, 7-day average resting heart rate, min and max, and min/avg/max per hour.

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": "get_heart_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD in the user's time zone. Leave empty for today.
include_samplesNoAlso return every sample (about one per 2 minutes).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description does add useful behavior beyond that: which aggregates are computed (daily min/max, 7-day rolling average, hourly buckets). It says nothing about cost or payload size, which matters given the optional per-sample mode.

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?

A single front-loaded sentence naming the resource and scope, followed by a compact enumeration of returned metrics. No filler, though the metric list is somewhat dense for one sentence.

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?

An output schema exists, so return values needn't be fully explained, and annotations cover the read-only nature. Parameters are fully documented in schema. The only real omission is sibling differentiation against HRV and HR-zone tools.

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%, so both parameters (date and include_samples) are fully documented in structured fields. The description adds only the 'one day' scoping, which aligns with but does not extend beyond the date parameter doc.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (heart rate) and scope (one day) and enumerates the returned metrics: resting HR, 7-day average, min/max, and hourly min/avg/max. It does not differentiate from siblings like get_hrv or get_heart_rate_zones, so an agent must infer the boundary from names alone.

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

Usage Guidelines3/5

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

Usage is implied: retrieve daily heart-rate summary for a single date. There is no explicit when-to-use/when-not guidance, no mention of how this differs from HR zone or HRV tools, and no note about the date default (that lives only in the schema).

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