Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_sleep

Read-only

Retrieve Garmin sleep duration, stages, scores, and overnight vitals for inclusive wake-up dates; defaults to the last 7 days (up to 90) and reports missing days explicitly.

Instructions

Sleep duration/stages in seconds, score and overnight vitals. Inclusive wake-up dates; defaults to the last 7 days, maximum 90. Missing days are explicit.

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

Input Schema

Name	Required	Description	Default
`end`	No
`start`	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.7/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely new behavior: units in seconds, inclusive wake-up date semantics, the default and cap on range, and that missing days are returned explicitly rather than omitted — meaningful return-shape context not in 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?

Three short, front-loaded sentences with essentially zero waste — payload first, then date semantics, then missing-data behavior. The telegraphic, fragment-heavy style slightly reduces readability but not information density.

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?

With an output schema present, the description needn't document return fields, and it still notes units, date semantics, range defaults, and missing-day handling. The remaining gap is the date string format, which matters for actually constructing a valid call.

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% and the two date parameters have no descriptions, so the description must carry them. It partially does: 'inclusive wake-up dates', default of last 7 days, and a 90-day maximum clarify the semantics of start/end, but the expected string format (ISO vs YYYY-MM-DD) is never stated.

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 the resource (sleep) and the payload (duration/stages in seconds, score, overnight vitals), so the agent knows exactly what it retrieves. It does not differentiate itself from sibling sleep tools such as garmin_api_sleep_daily or garmin_api_sleep_summaries, leaving ambiguity about which to pick.

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

Usage Guidelines3/5

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

Usage constraints are given (defaults to the last 7 days, maximum 90, inclusive wake-up dates), which implies how to call it. However there is no explicit statement of when to use this versus the several sibling sleep endpoints, so the agent must infer the choice.

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