Skip to main content
Glama

get_stats_range

Read-only

Retrieve per-day calorie and step totals across a date range in one request instead of calling daily stats repeatedly; partial and missing days are flagged for accurate averages.

Instructions

Get lightweight per-day calorie and step totals for a date range.

    Returns total/active/resting calories and steps for each day between
    start_date and end_date, inclusive, instead of the full get_stats
    payload per day. Use this for multi-day analysis (e.g. comparing
    measured intake/expenditure against Garmin's calorie model) instead
    of calling get_stats once per day.

    resting_calories is Garmin's bmrKilocalories field -- per Garmin's
    own documentation this is RMR (BMR plus sedentary-to-light movement),
    not true basal metabolic rate.

    is_partial is true for the current date, whose accumulator only
    covers elapsed hours so far -- treating it as a full day will
    overstate a mean. Days with no device data (e.g. before the account
    existed, or future dates within the range) return has_data: false
    and null values rather than zeros, so a missing day never silently
    enters an average as zero.

    Maximum range: 28 days per call (Garmin's own limit for this endpoint).

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

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses the 28-day endpoint limit, the is_partial flag for the current date and why it matters for means, and that missing days return has_data:false with nulls rather than zeros. It also flags that resting_calories is Garmin's bmrKilocalories (RMR, not true BMR), a semantic trap an agent would otherwise fall into.

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?

Purpose and the sibling comparison are front-loaded, and the caveat paragraphs each carry non-obvious information. The trailing Args block largely restates the schema titles, though the format and inclusivity details keep it from being pure waste.

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?

With no output schema, the description still tells the agent what each day contains (total/active/resting calories, steps) plus the is_partial and has_data flags. Combined with the range limit, an agent has everything needed to call this correctly and interpret the result.

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 the parameters, and it does: both dates are YYYY-MM-DD strings, the range is end-inclusive, and there is a hard 28-day ceiling. That compensates well for the bare schema, though no validation/error behavior for out-of-range or malformed dates is described.

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?

The opening sentence names a specific verb and resource ('per-day calorie and step totals for a date range') and immediately contrasts the scope with the sibling 'get_stats' full payload. An agent can distinguish this from get_stats 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 Guidelines4/5

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

It gives an explicit selection rule: use this for multi-day analysis 'instead of calling get_stats once per day.' It does not explicitly state the inverse (a single day should use get_stats), but the alternative and the condition are clear enough to route correctly.

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