Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_hrv_summaries

Read-only

Retrieve nightly Garmin HRV summaries over a date range to compare last-night and weekly averages against your baseline band and status for trend tracking.

Instructions

HRV summary per night over a date range: last-night average, weekly average, baseline band and status. Best for HRV trends.

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_hrv_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast date (YYYY-MM-DD), inclusive. Default: today.
start_dateNoFirst date (YYYY-MM-DD), inclusive. Default: 6 days before end_date.

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=true and openWorldHint=true, so the safety profile is covered. The description adds that results are aggregated per night, but it does not mention data latency, whether missing nights appear as gaps, or the maximum span allowed for the date range.

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?

Two short sentences, front-loaded with the resource and granularity before the payload list and the trend recommendation. Every clause carries information; nothing is padded or repeated.

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 an output schema present, the description need not explain return values, and annotations carry the read-only profile. What remains missing is only minor operational context such as maximum range length or handling of missing nights, which is not critical for a two-parameter 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 both parameters carry format and default explanations (YYYY-MM-DD, default today, default 6 days before end_date). The description only echoes the existence of a date range, adding no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific resource and granularity ('HRV summary per night over a date range') and enumerates the contents (last-night average, weekly average, baseline band, status), which is far more than a restatement of the name. It stops short of explicitly distinguishing itself from the sibling get_hrv, leaving the agent to infer that this is the aggregated view versus raw readings.

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?

'Best for HRV trends' implies a usage context, but it does not state when to prefer this over get_hrv or any other sibling, nor does it name an alternative. The guidance is suggestive rather than directive, so an agent still has to guess at selection criteria.

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