Skip to main content
Glama

getDailySummary

Read-only

Retrieve daily Garmin totals for steps, calories, stress, Body Battery, and resting heart rate for one date or a range up to 14 days.

Instructions

Daily user summary (steps, calories, stress, body battery, resting HR) for one date, or for up to 14 days (fromDate and toDate; the range answer has Garmin's v2 field names), yyyy-MM-dd. Use it for the totals of each day; for sleep use getSleep, for the Body Battery events getBodyBattery, and for the HR samples getDailyHeartRate.

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": "getDailySummary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate yyyy-MM-dd
toDateNoLast date yyyy-MM-dd, with fromDate
fromDateNoFirst date yyyy-MM-dd, with toDate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description adds real behavior: the 14-day maximum range and the fact that range results are shaped differently (v2 field names) from single-day results. It says nothing about response format otherwise or about behavior with zero dates, and there is no output schema to fall back on.

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 the resource and its metrics, then the date shapes, then the sibling routing — good ordering with no filler. The nested parenthetical '(fromDate and toDate; the range answer has Garmin's v2 field names)' is slightly dense but carries necessary information.

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?

Covers metrics, date formats, range limits, and sibling alternatives for a read-only tool with no output schema, which is nearly everything an agent needs. The one remaining gap is default behavior when none of the three optional parameters is provided.

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 meaning the schema does not: fromDate and toDate are a paired range with a hard 14-day cap, and the range response uses different (v2) field names than the single-date response. It does not state what happens when no date parameter is supplied, which keeps it below 5.

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?

Names a specific verb+resource ('Daily user summary') and enumerates the metrics returned (steps, calories, stress, body battery, resting HR), plus the two supported shapes: single date or a 14-day range. It also names the sibling tools that cover adjacent data, so an agent can distinguish it without opening any 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?

Explicitly states the selection rule ('Use it for the totals of each day') and routes the reader elsewhere for adjacent data: sleep to getSleep, Body Battery events to getBodyBattery, HR samples to getDailyHeartRate. This is explicit when-to-use plus named alternatives, with the boundary conditions spelled out.

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