Garmin MCP for macOS

by devnjw

Overview Schema Source Related Servers Discussions Admin

Python

Local

garmin_api_hrv_daily

Read-only

Fetch daily HRV summaries and raw readings from Garmin Connect by date, with a default 7-day range and 31-day maximum.

Instructions

Full daily HRV summary and readings. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

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

Input Schema

Name	Required	Description	Default
`calendar_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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, and non-destructive, so the safety profile is covered. The description adds useful behavioral context beyond that: raw JSON fields are not normalized, and the date-range defaults and 31-day cap constrain queries. It doesn't explain response shape, but the output schema exists for that.

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?

Three short sentences, front-loaded with the tool's identity and followed by the constraints that matter. Efficient with little waste, though the parenthetical about activity search pagination is slightly tangential to this tool.

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 read-only annotations and an output schema present, the description needn't explain return values, and it covers the key query constraints and the raw-JSON caveat. The main gap is sibling differentiation, but the core calling information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one optional parameter (calendar_date) with 0% schema description coverage, so the description should carry the load. It conveys that date ranges default to 7 days and cap at 31, which implies the parameter is an optional date selector, but it doesn't state the expected format or that leaving it null yields the default window.

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 clear resource and scope ('Full daily HRV summary and readings'), so an agent knows it retrieves daily HRV data. It doesn't explicitly differentiate from close siblings like garmin_api_hrv_summaries or garmin_hrv, leaving ambiguity about which HRV tool to pick.

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 description gives date-range defaults (7 days) and a maximum (31 days), implying how to use the tool across time windows. However, it never says when to prefer this over the many sibling HRV and summary tools, leaving alternatives inference-based.

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