Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_daily_stats

Retrieve Garmin Connect daily summary stats for a specific YYYY-MM-DD date, including steps, calories, resting heart rate, stress, body battery, and floors ascended.

Instructions

Get daily summary stats for one day: steps, calories, resting HR, stress, etc.

date must be "YYYY-MM-DD". Returns a JSON object with fields such as totalSteps, totalKilocalories, restingHeartRate, averageStressLevel, bodyBatteryHighestValue/LowestValue, and floorsAscended.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does identify the tool as a 'Get' read operation and lists example returned fields. However, it does not explicitly state read-only behavior, timezone semantics for the date, or what happens on days with missing data.

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 description is front-loaded with the purpose, followed by the date format and example return fields, and contains little wasted language. Listing output fields is somewhat redundant because an output schema exists, but it remains readable and appropriately sized.

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?

For a simple one-parameter read tool with an output schema, the description covers the purpose, the critical date format, and the kinds of metrics returned. The main remaining gaps are usage routing against siblings and timezone/edge-case behavior.

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% and the single required parameter is only typed as a string, so the description adds essential meaning by specifying that `date` must be formatted as "YYYY-MM-DD". It does not clarify timezone or local-vs-UTC interpretation, which keeps it from a 5.

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 states a specific verb and resource: getting daily summary stats for one day, with concrete metric examples like steps, calories, resting HR, and stress. It is clearly distinct from metric-specific siblings such as get_heart_rate or get_sleep, but it does not explicitly name or contrast those alternatives.

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?

The description implies use for a single day's aggregate stats but gives no explicit when-to-use guidance, exclusions, or comparison to alternatives like get_heart_rate, get_body_battery, or get_performance_metrics. An agent must infer routing from the tool name and purpose alone.

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