Skip to main content
Glama
Sign In
Garmin MCP Server

Garmin MCP Server

by JJRPF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_heart_rates

Get full heart rate time-series data for a date, providing 2-minute interval readings. Use when you need detailed heart rate records rather than a summary.

Instructions

Get full heart rate time-series data

Note: This returns detailed 2-minute interval data (~25KB). For a compact summary, use get_heart_rates_summary().

Args: date: Date in YYYY-MM-DD format

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It mentions the return type (detailed time-series) and size (~25KB), which gives some behavioral expectations. It does not explicitly state side effects, but 'get' implies read-only, which is acceptable.

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?

The description is succinct, with the purpose, a distinguishing note, and parameter format all in a few lines. No unnecessary details.

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

Completeness5/5

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

For a simple get operation with one parameter, the description is complete. It provides the tool's purpose, output characteristics, and the parameter format. The contrast with the summary tool adds context without excessive length.

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

Parameters5/5

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

The schema has one parameter (date) with no description, but the tool description adds 'Date in YYYY-MM-DD format', providing the required format and meaning. This fully covers the single parameter.

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?

The description clearly states the tool retrieves full heart rate time-series data for a given date, distinguishing it from the summary variant via 'full' and 'detailed'. The sibling list includes get_heart_rates_summary, which reinforces the distinction.

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 names the alternative tool get_heart_rates_summary() for compact summaries, implying this tool is for detailed data needs. The note about 2-minute intervals and ~25KB size further guides when to use it.

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