Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_daily_summaries

Read-only

Retrieve daily Garmin health summaries for a date range—steps, calories, heart rate, stress, Body Battery, hydration, respiration, and pulse ox—to see how your day or week went.

Instructions

One overview per day: steps and floors, calories (active, resting, total), heart rate (min, max, resting), intensity minutes vs goal, stress breakdown, Body Battery (min, max, charged, drained), hydration, respiration and pulse ox. The best single call for "how was my day/week". Durations are in milliseconds.

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_daily_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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavioral context: results are one row per day and durations are reported in milliseconds, a unit convention absent from the schema and annotations.

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?

Front-loaded with the core purpose and the metric inventory, followed by the usage recommendation and the millisecond unit note. The long metric list is dense but each item conveys real data coverage; there is no 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?

An output schema exists, so return structure needn't be explained, and date defaults live in the schema. What remains uncovered is edge behavior such as missing days or partial data, but for a read-only daily aggregation the definition is essentially complete.

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?

Both parameters are fully documented in the schema (date formats YYYY-MM-DD, inclusive bounds, today / 6-days-before defaults), so the description adds nothing about them. Baseline 3 applies when coverage is 100%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource ('one overview per day') and enumerates the exact metrics returned (steps/floors, calories, heart rate, intensity minutes, stress, Body Battery, hydration, respiration, pulse ox), which lets an agent distinguish it from narrower siblings like get_steps or get_heart_rate.

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?

"The best single call for 'how was my day/week'" gives explicit usage context and signals it as the aggregate entry point. It stops short of naming exclusions or alternatives (e.g., use get_sleep_summaries for sleep detail), so it is clear guidance without routing rules.

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