Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_sleep_summaries

Read-only

Retrieve Garmin sleep summaries for a date range to review nightly sleep data and spot gaps, including empty placeholders for days without records.

Instructions

Sleep summaries across a date interval, including empty placeholders from Garmin. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

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

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint=true, openWorldHint=true, and destructiveHint=false, the description adds useful behavior: empty placeholders are included, raw JSON fields are not normalized, and date ranges default to 7 days with a 31-day maximum. It does not state what happens if the range exceeds 31 days or how the raw payload should be interpreted.

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?

The description is compact and front-loads the resource and key caveats. The parenthetical about activity search pagination is slightly incongruous for a sleep tool, but the rest is efficient and earns its space.

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?

Given an output schema exists, the description need not explain return values. It covers the important behavioral caveats and limits, but is incomplete on date format conventions and sibling differentiation for a tool sitting among several sleep-related siblings.

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 description coverage is 0%, so the description must carry parameter meaning. It adds default and maximum range semantics, which is valuable, but it does not specify the expected date format, inclusivity, or how start_date and end_date interact when null or reversed.

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 clearly identifies the resource and scope: sleep summaries across a date interval, including empty placeholders from Garmin. It does not differentiate from close siblings like garmin_sleep or garmin_api_sleep_daily, so an agent cannot tell why to choose this tool over those.

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?

It gives date-range constraints (default 7 days, max 31 days) but no explicit guidance on when to use this tool instead of garmin_sleep, garmin_api_sleep_daily, or other sleep-related siblings. The parenthetical mention of activity search pagination is not enough to route between alternatives.

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