Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by ronkatz29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_resting_heart_rate

Retrieve your resting heart rate for any date to monitor cardiovascular recovery and baseline heart health.

Instructions

Get heart rate data (including resting HR) for a date.

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

Input Schema

NameRequiredDescriptionDefault
cdateNoDate in YYYY-MM-DD format. Defaults to today.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior1/5

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

No annotations provided, and description gives no behavioral details (e.g., read-only, authorization, rate limits). The description carries full burden for behavioral transparency but fails to disclose even basic traits like idempotency.

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?

Single sentence of 10 words, front-loaded and to the point. No wasted words. Could be slightly more informative without damaging conciseness.

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 simple 1-param tool with output schema and different siblings, the description is minimal but adequate. Tells what and when (date). Lacks behavioral context, but completeness is not severely lacking for a straightforward read tool.

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 description coverage is 100% (parameter 'cdate' has clear description). The description adds no parameter-specific meaning beyond schema; 'including resting HR' adds context for the tool but not for the parameter. Baseline 3.

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?

Describes verb 'Get', resource 'heart rate data (including resting HR)', and scope 'for a date'. Distinguishes from siblings (activities, sleep, body battery). Minor ambiguity about whether it returns only resting HR or broader HR data, but clear overall.

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?

No explicit guidance on when to use this tool versus alternatives. Only implicit context from date parameter. Siblings are different domains, so conflict is low, but no when/not-to-use info.

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