Skip to main content
Glama
Garmin Connect MCP

Garmin Connect MCP

by pedrokehl

Get Fitness Age

garmin_get_fitness_age
Read-onlyIdempotent

Retrieve Fitness Age for a chosen date, including chronological age, achievable and previous values, contributing factors, and improvement targets to track fitness progress.

Instructions

Get the latest Fitness Age as of a date: chronologicalAge, fitnessAge, achievableFitnessAge, previousFitnessAge, and the components behind it (BMI or body fat, resting heart rate, vigorous activity days/minutes) with improvement targets.

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": {
      "calendarDate": "<calendarDate>"
    },
    "name": "garmin_get_fitness_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendarDateYesReference date; the latest Fitness Age available on or before it is returned. Format YYYY-MM-DD, in the user's local calendar.
fullHistoryScanNoSearch the whole history for the latest value (Garmin default: true). If false, only the 28 days before calendarDate are considered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, and open-world. The description adds useful behavioral context by listing the exact output fields and components returned, though it does not discuss no-data or error behavior.

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?

The description is a single front-loaded sentence that names the action, date qualification, and return contents without redundancy.

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 no output schema, the description usefully enumerates the main return fields and components. Combined with fully documented input parameters, it gives the agent enough information to call and interpret the tool, though it omits empty-result behavior.

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%, so both calendarDate and fullHistoryScan are already well documented. The description reinforces the date-based lookup but adds no additional parameter semantics beyond the schema.

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 uses a specific verb and resource ('Get the latest Fitness Age') and enumerates the returned fields, making it clearly distinguishable from sibling wellness metrics like sleep, HRV, or body battery.

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 states the key usage context: retrieve the latest Fitness Age as of a given date. It does not explicitly name alternatives or when-not-to-use cases, but the metric-specific scope is clear enough for an agent to select it correctly.

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