Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Lander-garmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_fitness_age

Retrieve your Garmin fitness age with VO2 max, BMI/body fat, resting heart rate, and vigorous days for any date. See how these components shape your biological age.

Instructions

Garmin fitness age with its components (VO2 max, BMI/body fat, RHR, vigorous days).

Args: date: Calendar date in YYYY-MM-DD format. Defaults to today.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fitness_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo

Output Schema

NameRequiredDescriptionDefault
dataNoCompacted Garmin payload; null if unavailable.
noteNoExplains missing data or truncation.
paramsNoParameters used.
sourceYesGarmin Connect API method the data came from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description should disclose read-only behavior, permissions, or side effects. It only lists output components and the default date behavior; it does not explicitly confirm the operation is safe or describe rate/usage limits.

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 description is brief and front-loaded with the core resource, but the first sentence is a fragment without an explicit action verb. The Args block is clean and contributes value.

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 an output schema available and only one well-documented parameter, the tool is easy to invoke. It could be improved by adding a brief note about its relationship to fitness metrics tools, but it is not severely incomplete for a simple getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single date parameter is fully explained with format (YYYY-MM-DD) and default behavior (today), compensating for the 0% schema description coverage. This is exactly the semantic information an agent needs.

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 clearly identifies the resource (Garmin fitness age) and enumerates its components, which distinguishes it from generic metrics tools. However, it is a noun phrase rather than a verb+resource sentence, and it does not explicitly contrast with sibling tools like get_fitness_metrics.

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?

No guidance on when to choose this tool over siblings is provided. There is no mention of alternatives, exclusions, or prerequisites, leaving the agent to infer usage from the name alone.

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