Skip to main content
Glama

get_hrv_trend

Read-only

Retrieves daily HRV values and weekly rolling averages over a date range to detect baseline shifts linked to fatigue or recovery, helping adjust training load when HRV drops.

Instructions

Get HRV (Heart Rate Variability) trend over a date range.

    Returns daily HRV values and weekly rolling averages. Single-day HRV is too noisy
    to act on — use this tool to identify baseline shifts that signal accumulated fatigue
    or recovery. A drop of >10ms from the 7-day baseline warrants reducing training load.

    Recommended range: 7-21 days. Maximum: 30 days.
    Empty days are skipped; a failed daily request returns an error.

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End 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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_hrv_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds real behavioral detail on top: empty days are skipped and a failed daily request returns an error, plus the recommended and maximum date spans. That is meaningful context beyond the structured fields, though it says nothing about rate limits or latency for multi-day fetches.

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?

Front-loaded with purpose, then interpretation guidance, then range constraints, then argument formats — a sensible ordering with no filler. The coaching sentence about the 10ms drop is arguably beyond a tool description but is short and directly shapes correct invocation.

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?

With no output schema and no annotation coverage of return behavior, the description steps in to describe the returned series and the error path, which is what an agent needs. It is nearly complete for a two-parameter read tool; only edge-case handling for invalid or inverted dates is unstated.

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 carries the full burden and largely does: it specifies both parameters as YYYY-MM-DD dates and imposes a 30-day maximum span that the schema does not express. It does not clarify whether the range is inclusive of both endpoints or what happens if start_date exceeds end_date.

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 opens with a specific verb and resource ('Get HRV trend over a date range') and states the return shape ('daily HRV values and weekly rolling averages'). It is clear what the tool does, though it never explicitly distinguishes itself from the sibling get_hrv_data, so an agent must infer the difference from the word 'trend'.

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?

It gives a concrete decision rule — single-day HRV is too noisy, use this for baseline shifts signalling fatigue or recovery, and act when a drop exceeds 10ms from the 7-day baseline. It also prescribes a recommended 7-21 day range and a 30-day maximum. What it lacks is an explicit pointer to which sibling to use for raw/single-day values.

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