Skip to main content
Glama

Get day overview

garmin_get_day
Read-only

Retrieve a daily Garmin summary for any date, including steps, calories, sleep, HRV, stress, body battery, and activities. Missing sections return partial data or an error without blocking the rest.

Instructions

One day at a glance: daily summary (steps, calories, intensity minutes, resting HR, stress, body battery), last night's sleep, HRV, body battery, stress, and the day's activities. A section Garmin has no data for comes back as null or [], or as {"error": ...} when Garmin rejects that section's request; the other sections still load.

date: YYYY-MM-DD (default: today).

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

Input Schema

NameRequiredDescriptionDefault
dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already carry readOnlyHint and openWorldHint, so the safety profile is covered. The description goes beyond them with genuinely useful partial-failure semantics: missing sections return null or [] and a rejected section returns {"error": ...} while the rest still load — critical behavior for an aggregate tool whose sections can fail independently. It does not mention auth requirements or the cost/latency of a fan-out call.

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 overview claim is front-loaded, followed by the section inventory, then failure semantics, then the date convention — a sensible order with no filler. There is slight redundancy in that stress and body battery appear both inside the parenthetical summary list and as standalone sections.

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?

With no output schema, the description must convey the return shape, and it does: named sections, null/[] for absent data, and per-section error objects. For an aggregate fan-out tool this is close to sufficient; it could add whether the whole call is slow or whether the date defaults to the device's timezone, but nothing essential is missing.

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% for the single 'date' parameter, so the description must carry the burden — and it does, supplying the exact format 'YYYY-MM-DD' and the semantic default 'today'. That is meaningful added value over a bare untyped string property; only minor gaps remain (e.g., timezone handling).

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-plus-resource ('one day at a glance') and enumerates exactly what is returned: daily summary metrics, last night's sleep, HRV, body battery, stress and the day's activities. That inventory implicitly separates it from the single-metric siblings like garmin_get_steps or garmin_get_hrv, though it never names an aggregate-vs-individual distinction explicitly.

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?

Usage is only implied by the breadth of the returned sections; an agent can infer this is the aggregate overview to call instead of many single-metric getters, but the description never says 'use this when you want an overview, otherwise call X'. There are no exclusions, prerequisites, or guidance on cost/time tradeoffs versus calling the narrow siblings.

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