Skip to main content
Glama

garmin_recovery_status

Read-onlyIdempotent

Get a one-day recovery readiness snapshot that compares sleep, HRV, heart rate, breathing, stress, Body Battery recharge, and training load with your 28-day history to answer how recovered you are.

Instructions

Readiness snapshot for one day (default today): last night's sleep; HRV, resting HR, sleep HR, breathing rate and yesterday's stress each compared with the user's own previous 28 days (mean, SD, z-score, days of history); Body Battery recharge; training load of the last 7 vs 28 days; plain-language signals with the method used. Use this first for 'how recovered am I' questions.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDay, YYYY-MM-DD. Default: today.

Output Schema

NameRequiredDescriptionDefault
hrvNo
dateYes
methodYes
signalsYes
body_batteryNo
missing_dataNo
sleep_hr_bpmYes
training_loadNo
resting_hr_bpmYes
baseline_windowYes
last_night_sleepNo
stress_avg_yesterdayYes
sleep_respiration_brpmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-structured behavior: the comparison baseline is the user's own previous 28 days, the derived statistics include mean, SD, z-score and days of history, and plain-language signals come with the method used — all material to interpreting the result. It does not cover latency, data freshness, or behavior when fewer than 28 days of history exist, which keeps it below a 5.

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-loads the resource and scope, then packs the component list into one dense clause rather than a scannable list. Every clause carries information (no filler), but the single-sentence enumeration of seven metrics plus three derived quantities is heavier to parse than it needs to be.

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?

An output schema exists, so return-shape explanation is not required, yet the description still previews the main output domains and the statistical framing. For a read-only single-day aggregate with one optional parameter, an agent has everything needed to call it and to interpret the response.

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

Parameters3/5

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

With one parameter at 100% schema description coverage, the schema already documents the date format and default. The description restates 'one day (default today)' but adds no new meaning such as timezone handling or what happens on a future date, so the baseline of 3 applies.

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?

Names a specific resource and scope ('Readiness snapshot for one day (default today)') and then enumerates exactly what the snapshot contains — sleep, HRV, RHR, sleep HR, breathing rate, stress, Body Battery recharge, training load. This enumeration makes it distinguishable from the single-metric siblings like garmin_hrv, garmin_sleep, and garmin_body_battery without opening either schema.

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?

Gives explicit routing guidance with 'Use this first for "how recovered am I" questions,' which establishes priority over the narrower sibling tools. It stops short of stating when not to use it (e.g. for historical multi-day trends, where garmin_trends would apply), so it is clear context but not full when/when-not coverage.

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