Skip to main content
Glama

get_recovery_time_remaining

Read-only

Retrieves the remaining recovery time in hours for a given date using Garmin's Firstbeat recovery clock, and estimates today's value when snapshots are unavailable.

Instructions

Get remaining recovery time in hours for a day.

    This is the Firstbeat recovery clock shown on-device, distinct from
    Training Readiness score (missing on some devices such as Forerunner 255)
    and from Training Status ACWR. Training Readiness values are snapshots:
    remaining_hours and state describe the snapshot at as_of (Garmin's local
    timestamp when available), not a live countdown. remaining_hours_at_snapshot
    retains the same value explicitly. For today only, when snapshots are
    absent, the tool estimates remaining recovery by decaying recent activity
    assignments and reports the estimate's as_of time. Today uses the server's
    local date. Request failures are reported as errors, or source_errors when
    another source supplies usable data.

    Args:
        date: Date in YYYY-MM-DD format. Defaults to today.
    

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

Input Schema

NameRequiredDescriptionDefault
dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description goes far beyond by disclosing that values are snapshots at as_of rather than a live countdown, that today-only estimation exists and how it is derived (decaying recent activity assignments), that 'today' uses the server's local date, and that failures surface as errors or source_errors with fallback data. This is exactly the behavioral context annotations cannot carry.

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 the one-line purpose followed by disambiguation, then snapshot semantics and edge cases. The clause about remaining_hours_at_snapshot 'retaining the same value explicitly' is somewhat redundant, but since there is no output schema, naming those fields does useful work.

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?

For a single optional-date read with no output schema, the description covers the estimation fallback, snapshot timing, error paths and date default. The gap is what happens for a past date when no snapshot exists — only the today case is specified — leaving one branch of behavior undefined.

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% (only type/title/default), so the description must compensate and does: it specifies the YYYY-MM-DD format, the today default, and that 'today' resolves via the server's local date. It does not discuss timezone handling of an explicit date, so it is strong but not exhaustive.

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?

Opens with a specific verb, resource and unit: 'Get remaining recovery time in hours for a day.' It then explicitly separates the metric from Training Readiness score and Training Status ACWR, so an agent can tell which recovery-adjacent concept this returns without opening the 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?

It states the differentiator versus Training Readiness and ACWR, which implies when to prefer this tool, and it defines the estimation path ('For today only, when snapshots are absent...'). It stops short of an explicit 'use X instead when...' rule, so guidance is clear but not fully prescriptive.

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