Skip to main content
Glama

getFitnessAge

Read-only

Retrieve Garmin fitness age for a given date, including chronological age, achievable and previous fitness age, plus body-fat, vigorous-activity, and resting-heart-rate details.

Instructions

Garmin fitness age for a date, yyyy-MM-dd: fitnessAge, chronologicalAge, achievableFitnessAge and previousFitnessAge, and components: bodyFat, vigorousDaysAvg and vigorousMinutesAvg (per week) and rhr (resting HR), each with its value and, when Garmin suggests one, targetValue and potentialAge (the fitness age at the target). stale is Garmin's flag for an old value. Use it for fitness age; for the body fat trend use getWeight.

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": "getFitnessAge"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate yyyy-MM-dd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only cover readOnly/openWorld, so the description must carry the payload semantics — and it does, defining each return field, the per-component value/targetValue/potentialAge triple, and that 'stale' is Garmin's flag for an old value. Missing only edge behavior such as empty results or unsupported dates.

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?

Purpose and format are front-loaded in the first clause, and the final sentence handles disambiguation. The field enumeration is dense but justified because there is no output schema; a slightly tighter grouping of components would improve it.

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, describing the full return shape is essential and this definition does it thoroughly, including the meaning of 'stale' and target-derived fields. Only gaps are error/empty-result behavior and any freshness guarantees.

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?

One parameter with 100% schema description coverage; the schema already says 'Date yyyy-MM-dd'. The description repeats the format ('for a date, yyyy-MM-dd') but adds no meaning such as timezone handling or whether future dates are allowed. 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?

States a specific verb and resource ('Garmin fitness age for a date') and immediately enumerates the payload (fitnessAge, chronologicalAge, achievableFitnessAge, previousFitnessAge, components). It also names the sibling it is not for body-fat trends (getWeight), so an agent can distinguish it without opening the schema.

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?

Explicitly routes the agent: 'Use it for fitness age; for the body fat trend use getWeight.' That is a clear when-to-use plus a named alternative with its selecting condition. It stops short of stating exclusions such as date range limits or what happens for dates without data.

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