Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_sleep_summaries

Read-only

Retrieve compact nightly sleep summaries across a date range, including duration, stages, score, average heart rate, stress, SpO2 and respiration to track sleep trends.

Instructions

Compact sleep summary per night over a date range: duration, stages, sleep score, average heart rate, stress, SpO2 and respiration. Use get_sleep for one night in detail.

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_sleep_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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the key behavioral trait that results are compact per-night aggregates rather than detailed records. It does not mention range-length limits, pagination, or empty-night handling, but an output schema exists so return shape needn't be explained.

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 sentences, zero filler, with the scope and returned metrics front-loaded and the sibling routing last. Each clause earns its place.

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?

Complete enough for a two-parameter read-only summary tool: purpose, metric list, defaults via schema, return values via output schema, and a named alternative. The only gap is silent behavior for long ranges or missing nights, which is minor given the rich structured fields.

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 document format and defaults (YYYY-MM-DD, start defaults to 6 days before end_date, end defaults to today), so the schema does the heavy lifting. The description's 'date range' phrasing confirms intent but adds no syntax or constraint detail beyond the schema.

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 specific verb and resource ('Compact sleep summary per night over a date range') and enumerates the returned metrics (duration, stages, sleep score, heart rate, stress, SpO2, respiration). It also contrasts scope with the sibling get_sleep ('one night in detail'), so the agent can distinguish the two without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative tool and the condition that selects it: use get_sleep for a single night in detail, implying this tool is for multi-night ranges. 'Compact' vs 'in detail' gives a clear selection rule.

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