Garmin Coach MCP

get_training_status

Retrieve Garmin training status for a specific date, including VO2max and load balance.

Instructions

Get Garmin's aggregated training status for a date, including the most recent VO2max reading and load balance.

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

Input Schema

Name	Required	Description	Default
`date`	No	Date in YYYY-MM-DD format (defaults to today)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Oct 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the composition of the returned aggregate (VO2max reading + load balance), which is useful, but it says nothing about authentication requirements, data availability/latency, or what happens when no status exists for the given date. Read-only nature is only implied by the verb 'Get'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the core verb and resource, with the included data points as a trailing clarifier. No redundant or padded language.

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 one-parameter, read-only lookup with a fully documented schema and no output schema, the description covers what the tool returns at a high level. The main omission is routing guidance relative to the several overlapping training/VO2max siblings, which an agent might need to choose correctly.

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 100% and the single 'date' parameter already documents the YYYY-MM-DD format and the default-to-today behavior. The description only says 'for a date' and adds no format, range, or timezone semantics beyond the schema, so the baseline 3 applies.

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?

Names a specific verb ('Get') and resource ('Garmin's aggregated training status'), plus the two data points included (most recent VO2max and load balance). This helps distinguish it from siblings like get_vo2max and get_training_stress_balance, though it doesn't explicitly state how it differs from them or from get_training_readiness.

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?

The description gives no guidance on when to prefer this aggregated view over the sibling tools (get_training_readiness, get_vo2max, get_training_stress_balance) that surface the same underlying signals. Usage is only implied by the tool name and the word 'aggregated'.

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