Skip to main content
Glama

get_sleep_data

Read-only

Retrieve detailed sleep data for a specific date from Garmin Connect, including full sleep stages and metrics. Use for in-depth sleep analysis; for a compact summary, use get_sleep_summary().

Instructions

Get full sleep data with all details

    Note: This returns detailed sleep data (~50KB).
    For a compact summary, use get_sleep_summary().

    Args:
        date: Date in YYYY-MM-DD format
    

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a genuinely useful payload-size warning (~50KB), but says nothing about response shape, nesting, or whether missing data returns empty versus error — relevant since openWorldHint=true.

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 distinguishing detail and the sibling hand-off are front-loaded in two short sentences with no padding. Minor waste: 'with all details' and 'detailed sleep data' restate the same point.

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

Completeness5/5

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

For a single-parameter read-only tool with no output schema, the description covers what an agent needs: what it returns, why the payload is expensive, the required date format, and where to go for a lighter response.

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 0% and the only parameter is a bare string titled 'Date', so the description must carry the burden. It does supply the required format (YYYY-MM-DD), which is real added meaning, but nothing about timezone, date semantics, or what a single date returns for a whole 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?

"Get full sleep data with all details" gives a specific verb and resource, and the note explicitly contrasts this full-detail variant with get_sleep_summary. What 'all details' actually comprises (stages, HR, etc.) is left unspecified, which keeps it short of a 5.

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?

The note names the alternative (get_sleep_summary) and the condition that selects it (compact summary needed). No exclusion is given relative to get_sleep_summary_range, but the primary routing decision for this tool is clearly stated.

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