Fitbit MCP

Fitbit Daily HRV

fitbit_get_hrv_day

Read-onlyIdempotent

Retrieve your daily Heart Rate Variability (HRV) summary for any date when data is available. Requires heartrate scope and a supported device; not medical advice.

Instructions

Get HRV summary for a date when available. Requires heartrate scope and supported device/data. Not medical advice.

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

Input Schema

Name	Required	Description	Default
`date`	No	Date as yyyy-MM-dd or today. ISO date-times are accepted and reduced to the written calendar day.	today
`privacy_mode`	No	Optional per-call privacy override. Defaults to FITBIT_PRIVACY_MODE or structured. raw returns upstream Fitbit JSON. summary removes GPS/map details.
`response_format`	No		markdown

Output Schema

Name	Required	Description	Default
`data`	Yes
`endpoint`	Yes
`privacy_mode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.11Jul 30, 2026

changedInput schema / properties / date / description

Previous value: -"Date as yyyy-MM-dd or today."New value: +"Date as yyyy-MM-dd or today. ISO date-times are accepted and reduced to the written calendar day."

changedInput schema / properties / privacy_mode / description

Previous value: -"Optional per-call privacy override. Defaults to FITBIT_PRIVACY_MODE or structured. raw returns upstream Fitbit JSON. summary minimizes sensitive health and profile details."New value: +"Optional per-call privacy override. Defaults to FITBIT_PRIVACY_MODE or structured. raw returns upstream Fitbit JSON. summary removes GPS/map details."

First observedv0.4.5May 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds behavioral context about required scope and device support, plus the non-medical disclaimer. 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.

Conciseness5/5

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

Two short, efficient sentences. The first sentence states the purpose, the second adds constraints. No wasted words or redundant information.

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?

Given the presence of detailed annotations and an output schema (not shown), the description covers essential context: purpose, prerequisites, disclaimer. It lacks explanation of return values, but the output schema likely covers that. Adequate for a simple tool with few parameters.

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

Parameters2/5

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

The description does not add any parameter meaning beyond the input schema. Schema covers 2 of 3 parameters with descriptions (date and privacy_mode), but the third parameter (response_format) lacks a schema description and is not mentioned in the tool description. The description fails to compensate for this gap.

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 'Get HRV summary for a date' with a specific verb and resource. The name and title align, and the mention of HRV distinguishes it from sibling tools like fitbit_get_sleep_day or fitbit_get_heart_day.

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 prerequisites (heartrate scope, supported device/data) and a disclaimer (not medical advice), giving the agent context for when to use the tool. It lacks explicit alternatives or when-not-to-use guidance, but the prerequisites are clear.

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