Garmin MCP Server

by nitinmms

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_sleep

Read-only

Retrieve one night's sleep data—duration, stages, score, SpO2, respiration, and sleep stress—for the date you woke up.

Instructions

Get one night's sleep: duration, stages, sleep score, SpO2, respiration, sleep stress.

date is the calendar day the sleep ended on (the morning you woke up).

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

Input Schema

Name	Required	Description	Default
`date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by naming what data is returned and clarifying the meaning of the date, but it does not disclose behavior when date is omitted, how missing nights are handled, or timezone implications.

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?

The description is two compact sentences, front-loads the tool's purpose and returned fields, then adds the most important parameter semantic detail. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity read-only query with one optional parameter and no output schema, the description covers the main purpose, returned fields, and date meaning. However, it lacks date format/default behavior and does not route the agent away from similar sibling tools, so it is adequate but not fully complete.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It does so by explaining that `date` is the calendar day the sleep ended on, which is essential and non-obvious, though it omits the accepted format and whether omitting it defaults to today or the latest night.

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 states a specific verb and resource: 'Get one night's sleep,' and lists the returned data domains (duration, stages, sleep score, SpO2, respiration, sleep stress). It is clearer than a generic sleep lookup, but it does not distinguish itself from the sibling tool get_sleep_summaries.

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?

The description implies this is for a single night's sleep, but it provides no explicit when-to-use guidance or comparison with alternatives such as get_sleep_summaries, get_daily_summary, get_spo2, or get_stress. The date explanation helps interpret a call but does not tell the agent when this tool is preferred.

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