Skip to main content
Glama

garmin_daily_summary

Read-onlyIdempotent

Fetch per-day wellness totals including steps, distance, calories, heart rate, intensity minutes, stress, Body Battery, respiration and SpO2 for a chosen date range up to 366 days.

Instructions

Per-day wellness totals: steps, distance, calories, resting/min/max heart rate, intensity minutes, stress, Body Battery range, respiration, SpO2. Range up to 366 days, default last 7.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_daily_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days ending at end_date, used when start_date is omitted.
end_dateNoLast day, YYYY-MM-DD. Default: today.
start_dateNoFirst day, YYYY-MM-DD in the user's local calendar. Default: computed from end_date and days.

Output Schema

NameRequiredDescriptionDefault
toYes
daysYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description earns credit by adding the hard 366-day ceiling and the 7-day default window, which are real behavioral constraints an agent needs and which the annotations do not convey; it does not discuss rate limits or data availability gaps.

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?

Two sentences, zero filler. The metric inventory comes first and the range/default constraints are front-loaded in the second sentence, exactly the order an agent needs.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety semantics. What remains missing is any routing guidance against the many sibling wellness tools; otherwise the definition is sufficient to invoke correctly.

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 100%, so the baseline is 3, but the description adds a constraint absent from the schema: the days parameter caps at 366 and defaults to 7. That is genuine added meaning beyond the field descriptions, though the start_date/end_date interplay is still left entirely to the schema.

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?

"Per-day wellness totals" states a specific resource and granularity, and the enumerated metrics (steps, calories, resting/min/max heart rate, Body Battery, SpO2, etc.) make clear this is the multi-metric daily rollup. It stops short of explicitly distinguishing itself from single-metric siblings like garmin_heart_rate or garmin_body_battery, so the differentiation is only implied by the breadth of the metric list.

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

Usage Guidelines3/5

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

The range cap (366 days) and default window (last 7 days) imply the intended use case of pulling a recent or bounded history, but the description never says when to prefer this over garmin_trends, garmin_heart_rate, or garmin_sleep, nor does it name any exclusion. Usage is inferable but not guided.

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