Skip to main content
Glama

get_hrv_data

Read-only

Retrieve Heart Rate Variability (HRV) data for a specific date from Garmin Connect, optionally including detailed 5-minute readings to analyze recovery and stress trends.

Instructions

Get Heart Rate Variability (HRV) data

    Args:
        date: Date in YYYY-MM-DD format
        return_timeseries: If True, include detailed 5-minute HRV readings (can be large)
    

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

Input Schema

NameRequiredDescriptionDefault
dateYes
return_timeseriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral note — that return_timeseries produces detailed 5-minute readings that 'can be large' — but says nothing about rate limits, data availability, or what is returned when the flag is false.

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?

Two short, front-loaded lines: the purpose first, then per-argument notes. The docstring-style 'Args:' block is compact and contains no filler.

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

Completeness3/5

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

For a two-parameter read tool with annotations covering safety and no output schema, the essentials are present. However, it never describes what the non-timeseries response contains (summary metrics, baseline comparison, timezone handling), which would help an agent decide whether to request the large payload.

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 description coverage is 0% (only bare titles), so the description carries the full burden and does so: it specifies the date format YYYY-MM-DD and explains that return_timeseries includes 5-minute granularity readings. Only the default value is left to the schema, which is fine since the schema already states it.

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 verb and resource (get HRV data) and lists the arguments, so an agent can tell it retrieves per-day HRV metrics. It does not distinguish itself from the sibling get_hrv_trend, leaving the single-day vs. trend boundary to be inferred.

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 statement of when to use this tool versus alternatives such as get_hrv_trend, and no prerequisites or exclusions. The only implicit guidance comes from the required date parameter.

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