Fitbit MCP

Fitbit Daily Heart Rate

fitbit_get_heart_day

Read-onlyIdempotent

Fetch daily heart-rate zones and resting heart rate for a specific date to track cardiovascular patterns and recovery. Requires heartrate scope; not medical advice.

Instructions

Get daily heart-rate zones and resting heart rate. Requires heartrate scope. 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_heart_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

C2.9/5.0

Behavior2/5

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

The description adds little beyond the annotations, which already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The only additional note is 'Not medical advice,' which is a disclaimer rather than behavioral insight.

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, front-loaded sentences with no wasted words. Purpose and key requirement are stated immediately.

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?

For a simple read-only tool with annotations and an output schema, the description is adequate but lacks guidance on usage alternatives and parameter details. It is minimally viable but could be improved.

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 explain any parameters; the schema covers 67% of parameters (with enums and defaults), but the description adds no extra meaning. Baseline would be 3 for high coverage, but 67% is moderate and the description fails to compensate.

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?

Description clearly states it retrieves daily heart-rate zones and resting heart rate, with a specific verb and resource. While it doesn't explicitly distinguish from siblings like fitbit_get_heart_intraday, the purpose is unambiguous.

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?

The description provides a prerequisite ('Requires heartrate scope') but offers no guidance on when to use this tool versus alternatives (e.g., intraday) or when not to use it. No explicit usage context is given.

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