Skip to main content
Glama

get_sleep_summary_range

Read-only

Fetch nightly sleep summaries across a date range to analyze trends over weeks or months without repeated single-night calls.

Instructions

Get lightweight sleep summaries for every night in a date range.

    Returns the same curated metrics as get_sleep_summary (sleep score, duration,
    sleep stages, HRV, resting HR, etc.) for each night between start_date and
    end_date, inclusive. Use this instead of calling get_sleep_summary once per
    night when analyzing sleep trends over weeks or months.

    Note: Garmin Connect does not expose a native range endpoint for sleep, so
    this makes one request per night internally. Recommended range: up to a
    few weeks for quick checks. Maximum: 90 nights per call.
    Empty nights are skipped; a failed request stops the range and returns
    an error identifying the failed date.

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End 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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_sleep_summary_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only and non-destructive behavior, and the description adds substantial context beyond them: one internal request per night, empty nights skipped, and a failed request aborting the range with an error naming the failed date. These are non-obvious implementation traits an agent must know to interpret partial results.

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?

Front-loaded with purpose and the sibling comparison, then caveats, then args. The trailing Args block largely repeats the schema's parameter names plus formats already given, adding mild redundancy, but nothing is padded or ambiguous.

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 two-parameter read tool with no output schema, the definition covers what the return contains (same curated metrics as get_sleep_summary), the cost model, the size ceiling, and the failure mode. An agent has everything needed to call it correctly and interpret results.

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 burden, and it does specify the YYYY-MM-DD format and the inclusive semantics of start_date/end_date. It does not discuss ordering, timezone, or behavior when start is after end, so it stops short of full coverage.

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 lightweight sleep summaries for every night in a date range') and explicitly contrasts with the sibling single-night tool get_sleep_summary, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('Use this instead of calling get_sleep_summary once per night when analyzing sleep trends over weeks or months') plus a recommended range (a few weeks) and a hard maximum (90 nights), which is exactly the guidance needed to choose and bound the call.

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