Skip to main content
Glama

get_vo2max_trend

Read-only

Track daily VO2 max estimates across a date range to assess whether training is producing fitness gains or signaling plateau, insufficient stimulus, or overreaching.

Instructions

Get VO2 max trend over a date range.

    Returns daily VO2 max estimates from Garmin's FirstBeat algorithm. Use this to track
    whether training is producing fitness gains over weeks or months. Flat or declining
    VO2 max over 4+ weeks suggests insufficient training stimulus or overreaching.

    Note: VO2 max estimates are smoothed and update gradually — daily changes of <0.5
    are within normal noise. Focus on the 4-6 week trend direction.

    Garmin records a new VO2 max value only on days with a recompute (after an
    activity). Days in between carry the last known value forward and are marked
    with "carried_forward": true, matching the trend chart in Garmin Connect.
    Dated status values retain their measurement date. data_points counts
    displayed days, including carried-forward values.

    If historical values are unavailable, the current profile estimate is returned
    separately and is not represented as a historical trend point.
    Endpoint-specific failures remain visible in request_errors when a
    fallback succeeds. Authentication, rate-limit, and connection failures
    stop the request.

    Recommended range: 4-12 weeks. Maximum: 90 days.

    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_vo2max_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses substantial behavior: values are smoothed by FirstBeat, carried-forward days are flagged, the current profile estimate is returned separately when history is missing, endpoint failures surface in request_errors on fallback while auth/rate-limit/connection failures abort the request. That is exactly the kind of failure-mode and data-shape detail 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?

Purpose and interpretation lead, with caveats and argument notes following in a logical order; nearly every sentence carries information. It is slightly verbose in the middle (the carried_forward/data_points paragraph could be tightened), which keeps it off a 5.

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, the description steps in to describe the return shape (daily estimates, carried_forward flag, data_points semantics, separate current-profile estimate, request_errors). It is nearly complete for a two-param trend tool; only the exact response envelope structure is left unspecified.

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 coverage is 0% (bare string types with titles only), so the description must carry the load, and it does: it states both args, the YYYY-MM-DD format, the 90-day maximum, and the recommended 4-12 week span. This adds real constraint meaning the schema alone does not convey.

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?

The opening sentence names a specific verb and resource ('Get VO2 max trend over a date range'), and the metric-specific wording separates it cleanly from siblings like get_hrv_trend or get_training_load_trend. An agent can tell exactly what series it gets back 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 gives clear when-to-use context ('track whether training is producing fitness gains over weeks or months') plus interpretive guidance (flat/declining over 4+ weeks suggests under-stimulus or overreaching) and a recommended range of 4-12 weeks. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is strong 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