Skip to main content
Glama

get_training_status

Read-only

Retrieve Garmin training status for a given date, including training load, VO2 max, recovery, and readiness indicators to assess fitness and recovery.

Instructions

Get training status with curated metrics

    Returns comprehensive training status including load, VO2 max, recovery,
    and training readiness indicators.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds value by naming the categories of data returned (load, VO2 max, recovery, readiness), which tells the agent what to expect in the response, but it says nothing about data freshness, upstream service dependency, or failure modes for an open-world call.

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 definition is short and front-loads the purpose and return contents before the argument line. Minor waste in adjectives ('curated metrics', 'comprehensive') and the docstring-style Args block, but nothing structurally confusing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry the burden of describing the return value; listing the metric categories does that at a coarse level, which is adequate. What is missing for a single-date, open-world health-data call is the semantics of the date argument and any differentiation from the many sibling training-metric tools.

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 description coverage is 0% — the schema only declares 'date' as a string with no format. The description compensates partially by specifying 'YYYY-MM-DD format', which is genuinely useful. It does not clarify whether the date is a single-day snapshot, a reference point for a rolling window, or how timezone affects interpretation, so the single required parameter remains under-specified.

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?

The description gives a specific verb+resource ('Get training status') and enumerates the returned domains: load, VO2 max, recovery, and training readiness. However, it does nothing to distinguish itself from closely overlapping siblings such as get_training_readiness, get_training_load_balance, and get_training_effect, so an agent cannot tell which one to pick from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer for a narrower question. Given that several siblings cover the same metrics (readiness, load balance), the absence of routing guidance is a real gap.

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