Skip to main content
Glama
durely insights
by durely

Daily health and recovery

garmin_get_daily_health
Read-onlyIdempotent

Retrieve day-by-day wellness and recovery data—steps, heart rate, stress, Body Battery, sleep, and HRV—from a local cache. Aggregate by week or month for trend analysis.

Instructions

Get day-by-day wellness and recovery data, from the local cache (all history).

Per day: steps (+ goal), floors, resting/min/max heart rate, stress (average, max, % of the day at rest/low/medium/high), Body Battery (min, max, charged, drained), intensity minutes (moderate, vigorous), calories (total, active), respiration, hydration, plus that night's sleep (duration, score) and HRV (last-night average, status).

group_by="week" (Monday-based) or "month" aggregates: averages per day, minimums/maximums for min_hr/max_hr/stress_max, and totals plus per-day averages for steps and intensity minutes.

Defaults to the last 14 days. Daily rows are limited to 92 days per call; use group_by="week" or "month" for longer periods (e.g. a year by week). Today's values are partial.

Examples: "How's my recovery this week?" → defaults. "Resting HR trend this year" → start_date="2026-01-01", group_by="week".

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

Input Schema

NameRequiredDescriptionDefault
end_dateNoDefaults to today
group_byNoday
start_dateNoLocal calendar date, yyyy-MM-dd
response_formatNo'markdown' for readable text (default), 'json' for complete structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: data comes from a local cache covering all history, today's values are partial, and a hard 92-day row limit exists. It does not say what happens when the cache is empty or stale, which matters given a garmin_sync sibling.

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?

Front-loaded purpose sentence, then a compact field inventory, then aggregation semantics, limits, and examples in a clear progression. The dense metric list is information the agent needs to answer 'what can I ask this for', so nothing reads as filler.

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?

There is no output schema, and the description compensates by enumerating the returned metrics and the aggregation shape in detail. The one gap is operational: it says data comes from the local cache but never indicates that a sync may be required first or how to detect an empty cache, which is relevant given the garmin_sync and garmin_sync_status siblings.

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?

With 75% schema coverage the baseline is 3, and the description earns above that: group_by has no schema description yet the text explains week is Monday-based and what week/month aggregation actually computes (averages per day, min/max for HR and stress, totals for steps and intensity minutes). start_date/end_date semantics (default last 14 days, today partial) and the response_format tradeoff are also covered.

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 opening sentence gives a specific verb and resource (day-by-day wellness and recovery data) and enumerates the exact metrics returned, so an agent can tell this is the rolled-up daily wellness view rather than a single-metric tool. It does not explicitly contrast with overlapping siblings such as garmin_get_sleep, garmin_get_hrv, or garmin_get_intraday, so the boundary is inferable but not stated.

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

Usage Guidelines4/5

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

Usage is well scaffolded: the 14-day default, the 92-day cap on daily rows, and the rule to switch to group_by="week" or "month" for longer windows are all stated, plus two worked examples mapping a user question to parameters. What is missing is any explicit exclusion (e.g. when to prefer garmin_get_intraday for same-day detail or garmin_get_sleep for a single night).

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