Garmin MCP Lite

Overview Schema Source Related Servers Discussions Admin

garmin_hrv_status

Retrieve overnight heart rate variability status, baseline, and recovery guidance for a chosen date to assess readiness and training recovery.

Instructions

Get overnight HRV (Heart Rate Variability) status, baseline, and recovery guidance.

Args: date: Date in YYYY-MM-DD format (defaults to today).

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

Input Schema

Name	Required	Description	Default
`date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.10Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; "Get" plus the overnight framing makes clear this is a read of recorded sleep-window data, and it discloses the shape of the payload (status, baseline, guidance). It omits what happens when no data exists for the requested date, whether a device sync is required, and any date-range limits.

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?

A single front-loaded sentence stating what is returned, followed by a minimal Args block; nothing is padded. The Args line is slightly redundant with the schema but earns its place by adding the format and default.

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?

For a one-parameter read tool that already has an output schema, the description covers purpose, return contents, and parameter format. The missing pieces — empty-data behavior and timezone handling for 'today' on an overnight metric — are small relative to the tool's simplicity.

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 compensate for the single parameter, and it does: it specifies the YYYY-MM-DD format and that the value defaults to today. It does not clarify the timezone used to resolve 'today' for an overnight metric, which is the one meaningful gap.

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 gives a specific verb and resource ("Get overnight HRV status, baseline, and recovery guidance"), and the word "overnight" scopes it to sleep-period HRV. It does not distinguish itself from near-neighbors like garmin_hr_trend or garmin_training_status, so an agent must infer the boundary.

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?

Usage is implied by "recovery guidance" — an agent can infer this is for assessing recovery/readiness — but there is no explicit when-to-use, no exclusions, and no named alternative for general heart-rate trends or overall status.

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