Skip to main content
Glama

fitbit_get_hrv

Retrieve nightly HRV data (daily_rmssd and deep_rmssd) from Fitbit Premium. Returns cached data by default or fetches live from Fitbit API. Requires on-wrist sleep tracking for readings.

Instructions

Get nightly HRV (heart rate variability) data.

Returns data from the local cache by default. Use live=True to fetch from Fitbit API. Run fitbit_sync first to populate the cache.

HRV data is sparse: only nights with on-wrist sleep tracking produce readings. Requires Fitbit Premium for access to this endpoint.

Args: start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d". Default: last 30 days. end_date: End date as "YYYY-MM-DD". Default: today. live: If true, fetch directly from Fitbit API instead of cache.

Returns one entry per night with daily_rmssd and deep_rmssd (ms). RMSSD = root mean square of successive RR interval differences. Higher values generally indicate better recovery and parasympathetic activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNo
end_dateNo
liveNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main tool handler for fitbit_get_hrv. Decorated with @mcp.tool() and @require_auth. Accepts optional start_date, end_date, and live flag. Parses dates, then either fetches live from the Fitbit API via _fetch_live() or queries the local SQLite cache via db.query_hrv(). Returns formatted JSON response with HRV entries.
    @mcp.tool()
    @require_auth
    async def fitbit_get_hrv(
        start_date: str | None = None,
        end_date: str | None = None,
        live: bool = False,
    ) -> str:
        """Get nightly HRV (heart rate variability) data.
    
        Returns data from the local cache by default. Use live=True to fetch
        from Fitbit API. Run fitbit_sync first to populate the cache.
    
        HRV data is sparse: only nights with on-wrist sleep tracking produce readings.
        Requires Fitbit Premium for access to this endpoint.
    
        Args:
            start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d". Default: last 30 days.
            end_date: End date as "YYYY-MM-DD". Default: today.
            live: If true, fetch directly from Fitbit API instead of cache.
    
        Returns one entry per night with daily_rmssd and deep_rmssd (ms).
        RMSSD = root mean square of successive RR interval differences.
        Higher values generally indicate better recovery and parasympathetic activity.
        """
        start, end = parse_date(start_date, end_date, default_days=30)
    
        if live:
            entries = await anyio.to_thread.run_sync(lambda: _fetch_live(start, end))
        else:
            await anyio.to_thread.run_sync(lambda: auto_sync_if_stale("hrv"))
            def _query():
                conn = db.get_db()
                rows = db.query_hrv(conn, start.isoformat(), end.isoformat())
                conn.close()
                return rows
            entries = await anyio.to_thread.run_sync(_query)
    
        if not entries:
            return format_response({
                "message": "No HRV data found for this period.",
                "hint": "Try live=True to fetch directly from the API.",
            })
    
        return format_response({"hrv": entries, "count": len(entries)})
  • Input schema/type hints for the tool: start_date (optional str), end_date (optional str), live (optional bool, default False). Return type is str (JSON serialized).
    async def fitbit_get_hrv(
        start_date: str | None = None,
        end_date: str | None = None,
        live: bool = False,
    ) -> str:
        """Get nightly HRV (heart rate variability) data.
  • Tool registration via @mcp.tool() decorator on the mcp instance from src/fitbit_mcp/mcp_instance.py
    @mcp.tool()
  • Private helper function that fetches HRV data live from the Fitbit API using chunked date ranges (up to HRV_MAX_RANGE_DAYS=30 per request). Parses the response into a sorted list of dicts with date, daily_rmssd, and deep_rmssd.
    def _fetch_live(start_date, end_date) -> list[dict]:
        """Fetch HRV data directly from the API."""
        from ..config import HRV_MAX_RANGE_DAYS
        results = {}
        d = start_date
        while d <= end_date:
            chunk_end = min(d + timedelta(days=HRV_MAX_RANGE_DAYS - 1), end_date)
            path = f"/1/user/-/hrv/date/{d}/{chunk_end}.json"
            data = api.get(path)
            for entry in data.get("hrv", []):
                ds = entry.get("dateTime")
                if ds and "value" in entry:
                    results[ds] = {
                        "date": ds,
                        "daily_rmssd": entry["value"].get("dailyRmssd"),
                        "deep_rmssd": entry["value"].get("deepRmssd"),
                    }
            d = chunk_end + timedelta(days=1)
        return sorted(results.values(), key=lambda x: x["date"])
  • Database helper to query cached HRV data from the SQLite hrv table within a date range.
    def query_hrv(conn: sqlite3.Connection, start_date: str, end_date: str) -> list[dict]:
        rows = conn.execute(
            "SELECT * FROM hrv WHERE date >= ? AND date <= ? ORDER BY date",
            (start_date, end_date),
        ).fetchall()
        return _rows_to_dicts(rows)
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses caching behavior, conditions for data availability (on-wrist sleep), premium requirement, and even interprets RMSSD values. No side effects or alterations – fully transparent.

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?

Well-structured with leading summary then bullet details. Every sentence adds value. Could be slightly more compact but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and low schema coverage, description fully equips an agent: purpose, parameters, behavior, return values with interpretation, prerequisites, and constraints. Complete for correct invocation.

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

Parameters5/5

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

Schema has 0% description coverage, but description extensively covers each parameter: date formats, defaults, meaning of live flag. It adds full semantic context beyond the JSON schema.

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?

Specific verb+resource: 'Get nightly HRV (heart rate variability) data'. Clearly distinguishes from siblings like fitbit_get_activity, fitbit_get_sleep, etc.

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?

States default cache behavior, live flag for API fetch, prerequisite sync, and constraints (sparse data, premium requirement). Could mention when not to use but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/partymola/fitbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server