Skip to main content
Glama

get_training_load_trend

Read-only

Retrieve daily acute and chronic training load over a date range to judge whether training load is building steadily or spiking via Garmin's ACWR status.

Instructions

Get Garmin's daily acute and chronic training load over a date range.

    Returns, per day, Garmin's acute load (`atl`, the 7-day load), chronic load (`ctl`), their
    difference (`tsb` = ctl - atl), and Garmin's Acute:Chronic Workload Ratio (`acwr`,
    `acwr_status`). These are Garmin's dailyTrainingLoadAcute/Chronic values, not TrainingPeaks
    CTL/ATL: they are on Garmin's weekly load scale, so `tsb` is not comparable to TrainingPeaks
    TSB and TSB form thresholds do not apply. Use `acwr`/`acwr_status` (and the optimal chronic
    load range) to judge whether load is building steadily or spiking.

    Recommended range: 4-8 weeks. Maximum: 90 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_training_load_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, openWorld), and the description adds real behavior beyond them: empty days are skipped and a failed daily request returns an error rather than partial data. It also warns that tsb is on Garmin's weekly scale so TSB-form thresholds do not apply, which prevents a concrete misinterpretation. It does not discuss rate limits or caching, keeping it short of 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 purpose, then return semantics, then constraints, then Args, so an agent can stop reading early and still call it. The TrainingPeaks disambiguation is longer than strictly necessary but earns its place by preventing a real analytic error; nothing is filler.

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?

With no output schema, the description fully specifies the return shape per day (atl, ctl, tsb, acwr, acwr_status) and their scale semantics. Combined with the range limits and failure behavior, an agent has everything needed to call this correctly and interpret the result.

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% (bare titles only), so the description must carry parameter meaning, and it does: both dates are specified as YYYY-MM-DD, and the range guidance (4-8 weeks recommended, 90 days max) constrains the end_date-start_date span. It does not say whether dates are inclusive or how timezone affects the daily bucketing.

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?

Opens with a specific verb and resource: 'Get Garmin's daily acute and chronic training load over a date range,' and enumerates the returned metrics (atl, ctl, tsb, acwr, acwr_status). It sharply distinguishes these values from TrainingPeaks CTL/ATL/TSB, but never contrasts itself with the closely named sibling get_training_load_balance, leaving that differentiation to inference.

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 concrete operating context: recommended 4-8 week range, a hard 90-day maximum, and guidance to use acwr/acwr_status to judge whether load is building steadily or spiking. It does not state when to prefer this over the balance or status siblings, so the 'vs alternatives' half of the guidance is missing.

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