Skip to main content
Glama

garmin_heart_rate

Read-onlyIdempotent

Retrieve intraday Garmin heart rate for a chosen day, aggregated into local-time intervals with avg/min/max BPM, resting/min/max, and 7-day resting average.

Instructions

Intraday heart rate for one day, aggregated into local-time intervals (avg/min/max bpm per interval), plus resting, min, max and 7-day resting average.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDay, YYYY-MM-DD. Default: today.
interval_minutesNoAggregation interval in minutes: 5, 10, 15, 20, 30, 60, 120, 180 or 240. Default 60.

Output Schema

NameRequiredDescriptionDefault
dateYes
seriesYes
max_hr_bpmNo
min_hr_bpmNo
interval_minYes
no_data_reasonNo
resting_hr_bpmNo
resting_hr_7d_avg_bpmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are bucketed into local-time intervals and each bucket carries avg/min/max, alongside day-level resting, min, max and a 7-day resting average — useful for knowing what shape of data to expect.

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?

A single front-loaded sentence that states scope first and enumeration second, with no filler or redundant restatement of the tool name.

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 two optional parameters, full schema coverage, annotations, and an output schema, the description covers the essentials of what the tool returns and how it aggregates. Minor gaps remain around data availability/latency and timezone handling, which could affect interpretation of 'local-time' buckets.

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 interval_minutes, including allowed values and defaults) are already fully documented structurally. The description reinforces the meaning of interval aggregation ('local-time intervals') but adds no syntax or constraint detail beyond the schema, so 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 the exact resource and scope: intraday heart rate for a single day, with explicit return content (avg/min/max bpm per interval plus resting, min, max and 7-day resting average). It is highly specific but does not explicitly contrast itself with near-neighbors such as garmin_hrv or garmin_daily_summary, so sibling differentiation is left implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no conditions under which a different heart-rate/HRV/trends tool is preferable, and no mention of prerequisites or data-availability caveats. The only usage hint ('Default: today') lives in the schema, not the description.

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