Skip to main content
Glama

get_stats

Read-only

Retrieve daily health and activity summary for a specified date, including steps, calories, heart rate, stress, body battery, and sleep metrics.

Instructions

Get daily activity stats with curated essential metrics

    Returns a summary of daily health and activity data including steps,
    calories, heart rate, stress, body battery, and sleep metrics.

    Note: bmr_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. For the current date, all calorie and
    duration fields are a partial-day accumulator (elapsed hours so far),
    not a full-day total.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description goes well beyond them: it discloses that bmr_calories is really Garmin's bmrKilocalories/RMR, and that for the current date all calorie and duration fields are partial-day accumulators. That is exactly the kind of non-obvious behavior an agent would otherwise misreport as a full-day total.

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 purpose is front-loaded in the first line, followed by the return contents and the two caveats, which all earn their place. The trailing 'Args: date' block is largely redundant with the schema and adds some structural noise.

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?

There is no output schema, so the description appropriately enumerates the returned metric categories, and the caveats address the biggest interpretation risks. Remaining gaps are timezone and historical-data-availability, which matter for a date-parameterized tool but are secondary.

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 description coverage is 0%, so the description must carry the parameter, and it does only minimally by restating the format ('date: Date in YYYY-MM-DD'). It does not discuss timezone handling, whether historical dates are supported, or how far back data goes, leaving format as the only added meaning.

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 names a specific verb and resource ('Get daily activity stats') and enumerates the metric families returned (steps, calories, heart rate, stress, body battery, sleep). It implicitly separates itself from range/body siblings by saying 'daily', but it never names get_stats_range or get_stats_and_body, so the agent must infer the boundary.

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?

There is no explicit guidance on when to use this tool instead of the closely named siblings, and no stated preconditions or exclusions. The only usage-relevant note is the current-date partial-day caveat, which is a data-interpretation warning rather than selection guidance.

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