Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_daily_summary

Read-only

Retrieve a day's Garmin health summary—steps, energy, heart rate, stress, Body Battery, and intensity minutes—for a specified date or today in your configured timezone.

Instructions

Daily steps, energy, heart rate, stress, Body Battery and intensity minutes. Date YYYY-MM-DD; default today in the configured timezone.

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

Name	Required	Description	Default
`date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral detail about the default date resolving to 'today in the configured timezone', but says nothing about historical data availability, missing-data behavior, or the openWorldHint implication (live API calls). Adequate but not rich.

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 short sentences totalling under 25 words, front-loaded with the returned metrics and followed by the only parameter constraint. Nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return-value explanation is unnecessary, and the sole parameter is fully specified. The remaining gap is sibling disambiguation in an unusually crowded namespace of near-duplicate daily-summary tools, which the description does nothing to resolve.

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 optional date parameter, so the description must carry the burden — and it does, specifying the YYYY-MM-DD format and the 'today in the configured timezone' default. That is meaningfully more than the bare schema, though it does not mention date-range limits or invalid-format behavior.

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 first sentence enumerates exactly which metrics are returned (steps, energy, heart rate, stress, Body Battery, intensity minutes), which is a precise resource scope. However, there is no verb and no mention of how it differs from the many overlapping siblings (garmin_day, garmin_api_daily_summary, garmin_api_daily_summaries, garmin_body_battery), so an agent cannot disambiguate from the name/description alone.

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?

No when-to-use guidance or exclusions are provided. The description explains the date default but never says when to choose this over garmin_day, garmin_status, or the garmin_api_daily_summary siblings that appear to cover the same ground.

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