Skip to main content
Glama

Training and recovery status

get_training_status
Read-onlyIdempotent

Get an athlete's current load, readiness and injury-risk picture: CTL (fitness, 42-day training load), ATL (fatigue, 7-day load) and TSB (form, CTL minus ATL), fitness, fatigue and recovery scores, readiness with reason codes, the daily training status, 7- and 30-day rolling load and recovery metrics, the fitness trend and active plans. get_athlete_profile gives goals, zones and personal bests.

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": {
      "athlete_id": "<athlete_id>"
    },
    "name": "get_training_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
athlete_idYesThe athlete's user id: get_current_user's athlete_id for the connected account, or an id from get_coach_athletes or find_athlete.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
errorNo
statusNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
warningsNo
next_stepNoWhat can be done next, for example after a failure.
athlete_idNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
user_contentNoFields in this result that people wrote.
fitness_trendNo
weeks_returnedNo
rolling_metricsNo
training_statusNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / $defs / Activity / properties / content_blocks / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "items": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "integer"
      -          },
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "boolean"
      -          },
      -          {
      -            "items": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "integer"
      -                },
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "boolean"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "type": "array"
      -          },
      -          {
      -            "$ref": "#/$defs/LocalizedText"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "type": "array"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "items": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "boolean"
      +          },
      +          {
      +            "items": {
      +              "anyOf": [
      +                {
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "integer"
      +                },
      +                {
      +                  "type": "number"
      +                },
      +                {
      +                  "type": "boolean"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "$ref": "#/$defs/LocalizedText"
      +          },
      +          {
      +            "items": {
      +              "type": "array"
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / $defs / Activity / properties / content_blocks / description
      Previous value: -"Interval rows; each row's values follow content_block_fields."New value: +"Workout steps as rows whose values follow content_block_fields; an interval's blocks value is its nested steps as rows in the same columns."
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description isn't burdened with safety claims. It adds real value by unpacking the domain semantics — CTL is 42-day load, ATL is 7-day load, TSB is CTL minus ATL — and by flagging that readiness comes with reason codes and that the view is derived/rolling. It stops short of saying how fresh or frequently recomputed these values are.

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?

The purpose and metric list are front-loaded, and the sibling-routing sentence is placed last where it belongs. The single long enumerative sentence is dense and has mild redundancy — 'fitness, fatigue and recovery scores' partially restates the CTL/ATL/TSB gloss — but almost every clause carries distinct content.

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 an output schema present, the description doesn't need to detail return structure, yet it usefully previews the major fields so the agent can decide whether this call answers the question. Combined with 100% schema coverage on the one parameter, an agent has enough to invoke this correctly; only data-freshness expectations are left unstated.

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?

Schema coverage is 100% and the single athlete_id parameter is already fully documented in the schema, including where to obtain it (get_current_user, get_coach_athletes, find_athlete). The description adds no parameter-level meaning beyond that, so the baseline 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?

The description opens with a specific verb and resource ('Get an athlete's current load, readiness and injury-risk picture') and then enumerates the concrete payload: CTL, ATL, TSB, readiness with reason codes, daily training status, rolling 7/30-day metrics, fitness trend and active plans. This is far more specific than the title, and the closing sentence about get_athlete_profile makes the boundary between the two tools explicit.

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 supplies a clear routing rule: use this for load/readiness/risk, use get_athlete_profile for goals, zones and personal bests. That is a concrete alternative with a selection condition. What's missing is any exclusion such as when this is redundant with get_activities or when a stale/absent status should divert the agent elsewhere.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources