Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_heart_rate

Retrieve a one-day heart rate summary for a specified date, including minimum, maximum, resting heart rate, and seven-day average resting heart rate. Returns compact JSON without per-minute values.

Instructions

Get heart rate summary for one day.

date must be "YYYY-MM-DD". Returns a JSON object with minHeartRate, maxHeartRate, restingHeartRate, and lastSevenDaysAvgRestingHeartRate. The per-minute heartRateValues time series is stripped to keep the response small.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it enumerates the returned fields and, crucially, discloses that the per-minute heartRateValues time series is stripped to keep the response small. That truncation behavior is the kind of thing an agent could not learn from structured fields. It does not state read-only semantics explicitly, but the verb "get" makes that unambiguous.

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?

Three short sentences, front-loaded with the purpose, then the required format, then the return shape. No filler; the format constraint is highlighted in backticks where an agent will notice it.

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?

For a single-parameter read tool this is nearly complete: format is pinned, return fields are named, and the payload-trimming behavior is disclosed. The only gap is the ambiguous notion of "one day" (local vs UTC boundary) and no pointer to alternatives for multi-day or intraday needs.

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 0% – the schema only declares `date` as an unformatted string. The description compensates by mandating the "YYYY-MM-DD" format, which is exactly the missing information needed to call the tool correctly. It does not address timezone or day-boundary semantics, so not a full 5.

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?

"Get heart rate summary for one day" gives a specific verb (get) and resource (heart rate summary) with an explicit scope (one day). It is clearly not a list or activity-detail tool, though it does not explicitly distinguish itself from the nearby get_daily_stats or get_activity_hr_zones siblings.

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 only implied: the agent can infer it should call this for a single day's heart rate, but nothing states when to prefer it over get_daily_stats (broader daily metrics) or get_activity_hr_zones (per-activity zones). No exclusions or alternatives are named.

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