Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_heart_rates

Read-only

Fetch heart rate data for a specific date (YYYY-MM-DD) from Garmin Connect to review daily heart-rate readings without modifying your account.

Instructions

Fetch available heart rates data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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": {
      "cdate": "<cdate>"
    },
    "name": "get_heart_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description repeats 'read-only' and adds source context ('Garmin Connect'), which is mildly useful, but it does not add meaningful behavioral detail such as rate limits, data granularity, or what is returned. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the operation, but it redundantly states the date format twice: once in the main clause and again in the parenthetical. The repeated 'YYYY-MM-DD' phrasing and duplicated read-only context reduce efficiency.

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?

An output schema exists, so return values need not be described. Annotations cover the safety profile for this simple read-only tool. However, the description remains incomplete because it does not clarify the dataset or differentiate this tool from sibling heart-rate endpoints, which is important given the crowded sibling list.

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?

Schema coverage is 0%, so the description must carry all parameter meaning. It does provide the required format for 'cDate' as YYYY-MM-DD, but it does not explain the parameter's semantics beyond format, such as whether it is a calendar date, local date, or how it interacts with the returned heart-rate data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Fetch available heart rates data') and identifies the source as Garmin Connect, but 'available heart rates data' is ambiguous. It does not distinguish this tool from close siblings such as get_daily_heart_rate_stats or get_rhr_day, leaving the agent unsure what specific heart-rate dataset is returned.

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?

There is no guidance on when to use this tool versus the many sibling heart-rate tools. The description only restates the required date format, so the agent must infer the use case from the name 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