Skip to main content
Glama

get_fitnessage_data

Read-only

Retrieve Garmin fitness age data for a specific date, with optional details on BMI, resting heart rate, vigorous activity, targets, and improvement suggestions.

Instructions

Get fitness age data

    Args:
        date: Date in YYYY-MM-DD format
        details: If True, include component breakdown (BMI, RHR, vigorous activity)
                 with targets and improvement suggestions
    

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

Input Schema

NameRequiredDescriptionDefault
dateYes
detailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing what the optional details flag returns (BMI, RHR, vigorous activity with targets and improvement suggestions), but says nothing about missing-data handling, permissions, or rate limits.

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?

Two short, front-loaded lines with zero filler; the purpose comes first and each argument note adds concrete meaning rather than restating the parameter name.

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 two-parameter read-only metric fetch with full annotation coverage and no output schema, the description supplies enough to call it correctly and even sketches the richer return shape. Lacking only guidance on error/empty responses for dates without data.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does: it specifies the date string format (YYYY-MM-DD) and explains that details=True expands the response into a component breakdown with the specific components named. The default of false is left to the schema, a minor gap.

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?

States a specific verb+resource: retrieves fitness age data for a date. The resource is distinct enough from sibling metric getters (HRV, sleep, steps) that an agent can identify the right tool, though the description never explicitly contrasts itself with them.

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 only implied by the required date argument and the optional breakdown flag; there is no explicit statement of when to call this versus other fitness/health metric tools, nor any prerequisites or exclusions.

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