Skip to main content
Glama
Garmin Health Connect

Garmin Health Connect

by NevoNadav

garmin_fitness_age

Read-onlyIdempotent

Retrieves your Garmin fitness-age estimate for a specified calendar date, giving a clear read on how your fitness compares to your actual age.

Instructions

Read Garmin's latest available fitness-age estimate as of this calendar date.

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": {
      "day": "<day>"
    },
    "name": "garmin_fitness_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context by clarifying that it returns the latest available estimate as of the given date, which helps interpret cases where no same-day estimate exists.

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 with no redundant or wasted language. It immediately states the operation and the temporal scope.

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 simple one-parameter read-only tool with an output schema and strong safety annotations, the description is largely complete. It could mention behavior when no estimate is available, but the output schema can carry return-value details.

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?

There is one required parameter, day, and the schema description coverage is 0%, so the description must carry semantic weight. The phrase 'as of this calendar date' clarifies that day anchors the requested estimate, but it does not add details beyond the schema's date format or explain timezone/future-date 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 uses a specific verb and resource: read Garmin's latest fitness-age estimate. It does not explicitly distinguish this tool from sibling Garmin metrics tools, so it is clear but lacks sibling differentiation.

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?

Usage is implied by the stated purpose and the calendar-date framing, but there is no explicit guidance on when to use this tool versus related Garmin health and daily-metric tools. No exclusions or alternatives are mentioned.

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