Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_training_status

Retrieves Garmin training status for a specified date, including fitness trend, training load, VO2 max, and heat or altitude acclimation.

Instructions

Get training status for a given day: fitness trend, load, VO2 max, acclimation.

date must be "YYYY-MM-DD". Returns a JSON object with mostRecentTrainingStatus (training status, acute/chronic training load), mostRecentVO2Max, and heatAltitudeAcclimationDTO.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does partially meet it by naming the returned JSON shape and its three top-level fields. It omits operationally important behavior: what happens on a day with no recorded data, whether `mostRecent*` fields return stale values, and whether any scope/permission constraints apply.

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?

Three short sentences, front-loaded with the purpose and then the parameter format and return shape; nothing is padded. The return-field list is somewhat redundant given an output schema exists, but it aids scanning rather than obstructing it.

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?

For a single-parameter read tool with an output schema, the description covers purpose, parameter format, and response contents. It still leaves open the meaningful edge cases (no data for the date, staleness of mostRecent* values), which matters for a day-indexed longitudinal metric.

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% (the `date` property has only a type, no description), but the description supplies the required format "YYYY-MM-DD" and ties the parameter to the day of the requested data. That is exactly the compensating detail the schema lacks, though it never states timezone or range/validity behavior.

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 opens with a specific verb and resource ("Get training status for a given day") and enumerates the domains covered: fitness trend, load, VO2 max, acclimation. It does not differentiate from nearby siblings such as get_performance_metrics or get_daily_stats, which plausibly overlap on load/VO2 max, so an agent must still infer the boundary.

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 when-to-use guidance and no named alternative; the only guidance is a date-format constraint. An agent cannot tell from the text whether this supersedes get_performance_metrics or get_daily_stats for the same day.

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