Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_sleep

Retrieve a compact JSON sleep summary for the night ending on a specified date, including sleep stages, scores, average HR/SpO2/respiration/stress, overnight HRV, and resting heart rate.

Instructions

Get sleep summary for the night ending on the given date.

date must be "YYYY-MM-DD" (the calendar date the sleep session ends on). Returns a JSON object with the daily sleep summary (dailySleepDTO: sleep stages in seconds, sleep scores, average HR/SpO2/respiration/stress) plus overnight HRV and resting HR. Per-minute sleep-stage and movement arrays are stripped to keep the response small.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "get_sleep"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

No annotations exist, so the description carries the full burden and does reasonably well: it lists what the payload contains (sleep stages in seconds, scores, average HR/SpO2/respiration/stress, overnight HRV and resting HR) and explicitly notes that per-minute stage/movement arrays are stripped to keep responses small. It omits failure behavior (missing data, auth requirements).

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?

Three short sentences, front-loaded with purpose then the date constraint, then the payload. Nothing is padded and the truncation note is stated as a fact rather than a caveat essay.

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?

A one-parameter read tool with an output schema and no annotations; the description covers format, date semantics, and the payload contents, which is enough to call it correctly. The only gap is edge-case behavior when no sleep exists for that date.

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 coverage is 0%, so the description must carry the parameter meaning, and it does: format (YYYY-MM-DD) and semantics (the night ending on that calendar date, not the start date). It does not discuss timezone handling or behavior when no sleep was recorded.

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 ("Get sleep summary") plus the precise scope ("for the night ending on the given date"). No sibling tool covers sleep, so there is no ambiguity to resolve against the activity/heart-rate tools listed.

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?

Gives the operative usage rule for the single input: the date is the calendar date the sleep session ends on, and it must be YYYY-MM-DD. No when-not-to-use guidance is offered, but there is no competing sleep tool to route away from.

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

Deploy Server

Other Tools