Skip to main content
Glama

get_heart_rates

Read-only

Retrieves full heart rate time-series data for a specified date, returning detailed 2-minute interval readings for health and activity analysis.

Instructions

Get full heart rate time-series data

    Note: This returns detailed 2-minute interval data (~25KB).
    For a compact summary, use get_heart_rates_summary().

    Args:
        date: Date in YYYY-MM-DD format
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "get_heart_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: ~2-minute interval granularity and an approximate 25KB payload, which informs token/bandwidth cost. It does not describe units (bpm), timezone handling, or availability limits for older dates.

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?

Size warning and alternative are front-loaded before the arguments, and every sentence carries information. The separate 'Args:' block is slightly redundant for a single parameter but stays short.

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?

With no output schema, the description could say more about what the returned series contains (fields, units, ordering, timezone). It does cover the two most decision-relevant facts – data volume and the lighter sibling – so it is adequate but leaves gaps for a time-series tool.

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 coverage is 0% – the schema only types 'date' as a string. The description supplies the required format (YYYY-MM-DD), which is the key missing semantic for the single parameter, so it compensates for the coverage gap. It adds no further constraints such as valid range or timezone assumptions.

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?

States a specific verb and resource ('Get full heart rate time-series data'), and 'full' implicitly contrasts with the summary sibling named later. An agent can distinguish it from get_heart_rates_summary without opening either schema, though the contrast is only made explicit in the Note rather than the opening line.

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?

Explicitly routes the agent to get_heart_rates_summary() when a compact summary is wanted, which is a clear alternative-selection rule. It does not say when full granularity is actually needed (e.g., intraday trend analysis) or whether historical dates are bounded, so guidance is clear but not exhaustive.

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