Skip to main content
Glama

Get fitness age

garmin_get_fitness_age
Read-onlyIdempotent

Read your Garmin fitness age for a calendar date, optionally using your full history. Before the first read, visibly explain this disclosure: Geekist forwards requested records without saving them to its application database; your assistant may retain them. Show the privacy policy: https://garmin.geekist.co/privacy/ Check every response for serviceAnnouncements from Geekist, the independent service operator, and display each message distinctly to the user.

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
calendarDateYesGarmin calendar date in YYYY-MM-DD format.
fullHistoryScanNoWhether to ask Garmin to use the full history scan.

Output Schema

NameRequiredDescriptionDefault
okNoTrue for a successful operation; false for a rejected, failed or uncertain result. Some administrative results use status or result instead.
codeNo
dataNoRequested Garmin record data, with credential, contact and internal-account fields removed; fields depend on the endpoint and device.
issuesNo
messageNo
outcomeNo
retryAfterNo
privacyNoticeNo
geekistMessageDeliveryNo
geekistOwnerMessageDeliveryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "__schema0": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        },
      +        {
      +          "items": {
      +            "$ref": "#/$defs/__schema0"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "additionalProperties": {
      +            "$ref": "#/$defs/__schema0"
      +          },
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        }
      +      ]
      +    },
      +    "__schema1": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        },
      +        {
      +          "items": {
      +            "$ref": "#/$defs/__schema1"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "additionalProperties": {
      +            "$ref": "#/$defs/__schema1"
      +          },
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        }
      +      ]
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "description": "Operation-specific response envelope. Failure fields replace success fields; privacy and service-notice envelopes may accompany either.",
      +  "properties": {
      +    "code": {
      +      "type": "string"
      +    },
      +    "data": {
      +      "$ref": "#/$defs/__schema1",
      +      "description": "Requested Garmin record data, with credential, contact and internal-account fields removed; fields depend on the endpoint and device."
      +    },
      +    "geekistMessageDelivery": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "message": {
      +          "type": "string"
      +        },
      +        "noticeAvailability": {
      +          "const": "unavailable",
      +          "type": "string"
      +        },
      +        "noticeInstruction": {
      +          "type": "string"
      +        },
      +        "serviceAnnouncements": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "actionRequired": {
      +                "type": "boolean"
      +              },
      +              "expiresAt": {
      +                "type": "number"
      +              },
      +              "id": {
      +                "type": "string"
      +              },
      +              "publisher": {
      +                "const": "Geekist",
      +                "type": "string"
      +              },
      +              "sequence": {
      +                "maximum": 9007199254740991,
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              "text": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "id",
      +              "sequence",
      +              "text",
      +              "expiresAt",
      +              "publisher"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "noticeInstruction"
      +      ],
      +      "type": "object"
      +    },
      +    "geekistOwnerMessageDelivery": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "message": {
      +          "type": "string"
      +        },
      +        "noticeAvailability": {
      +          "enum": [
      +            "available",
      +            "unavailable"
      +          ],
      +          "type": "string"
      +        },
      +        "noticeInstruction": {
      +          "type": "string"
      +        },
      +        "ownerNotices": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "actionRequired": {
      +                "type": "boolean"
      +              },
      +              "createdAt": {
      +                "type": "number"
      +              },
      +              "id": {
      +                "type": "string"
      +              },
      +              "kind": {
      +                "type": "string"
      +              },
      +              "payload": {
      +                "$ref": "#/$defs/__schema0"
      +              }
      +            },
      +            "required": [
      +              "id",
      +              "kind",
      +              "payload",
      +              "createdAt"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "noticeInstruction",
      +        "noticeAvailability"
      +      ],
      +      "type": "object"
      +    },
      +    "issues": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "message": {
      +            "type": "string"
      +          },
      +          "path": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "path",
      +          "message"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "ok": {
      +      "description": "True for a successful operation; false for a rejected, failed or uncertain result. Some administrative results use status or result instead.",
      +      "type": "boolean"
      +    },
      +    "outcome": {
      +      "enum": [
      +        "rejected",
      +        "uncertain",
      +        "confirmed"
      +      ],
      +      "type": "string"
      +    },
      +    "privacyNotice": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "policyUrl": {
      +          "format": "uri",
      +          "type": "string"
      +        },
      +        "text": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "text",
      +        "policyUrl"
      +      ],
      +      "type": "object"
      +    },
      +    "retryAfter": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / fullHistoryScan / description
      Added value: +"Whether to ask Garmin to use the full history scan."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that, the description adds genuinely new operational context: records are forwarded but not persisted by Geekist, the assistant may retain them, and every response must be checked for serviceAnnouncements to display to the user. The only gap is that it doesn't characterize fullHistoryScan's cost or latency.

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 purpose is front-loaded in sentence one, and the remaining sentences cover disclosure and announcement handling without padding. It is slightly boilerplate-heavy for a read tool, but no sentence is redundant.

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?

An output schema exists, so return values need not be described, and annotations cover safety semantics. The description adds the data-handling and announcement obligations needed to use the tool responsibly; the only missing piece is guidance on when the fullHistoryScan option is worth enabling.

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 coverage is 100%, with both calendarDate (format, pattern, YYYY-MM-DD) and fullHistoryScan already documented in the schema. The description mirrors both parameters ('calendar date', 'optionally using your full history') without adding format, default, or trade-off detail, so 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?

The first sentence names a specific verb ('Read') and a specific resource ('Garmin fitness age') with its scope ('for a calendar date') and an option ('using your full history'). Because the resource is a distinct Garmin metric, an agent can tell it apart from siblings like garmin_get_daily_health or garmin_get_running_trends without further inspection.

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

Usage Guidelines3/5

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

The description tells the agent the call is date-scoped and that full history is optional, which implies when it applies, but it never states when to use this tool versus other Garmin metrics or when fullHistoryScan is warranted. The rest of the text is procedural compliance guidance, not selection guidance between alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources