garmin-connect-mcp

Overview Schema Source Related Servers Discussions Admin

get_heart_rate

Retrieve resting, lowest, highest, and seven-day average resting heart rate for a specific day. Provide a date like "today" or "2026-08-18" to get heart rate insights.

Instructions

Heart rate for one day: resting, lowest, highest and the seven-day average resting heart rate.

Args: day: For example "today", "yesterday" or "2026-08-18".

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": "get_heart_rate"
  }
}

Input Schema

Name	Required	Description	Default
`day`	No		today

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not state whether the tool is read-only, requires authentication, has rate limits, or what happens if no data exists for the requested day. The description implies a safe read operation but does not confirm it.

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 short and front-loaded with the tool's output. Every sentence adds value, but the 'Args:' section is somewhat redundant with the schema, though it provides useful examples. Could be slightly tighter by integrating examples into the main text.

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?

Given the tool has an output schema, the description need not detail return fields, but it does list key returned metrics. However, it omits behavioral context (e.g., error handling, no-data cases) and usage guidance for alternative tools. Overall adequate for a simple retrieval tool but not fully comprehensive.

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%, so the description must explain the parameter. It does this effectively by giving concrete example values for the 'day' parameter (today, yesterday, date format), adding meaning beyond the schema's default value.

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 returns heart rate data for one day, including resting, lowest, highest, and a seven-day average. This is specific and distinct from sibling tools like get_hrv, get_steps, or get_sleep, which focus on different health metrics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides examples for the 'day' parameter ('today', 'yesterday', '2026-08-18'), which guides usage. However, it does not explicitly exclude cases where broader date ranges are needed (e.g., via get_date_range_summary) or clarify when not to use this tool versus alternatives.

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