Skip to main content
Glama

get_acclimation

Read-only

Retrieves heat and altitude acclimation status for a given date, including heat acclimation percentage, trend label, and prior readings to judge warm-weather race readiness.

Instructions

Get heat and altitude acclimation status for a given date.

    Garmin tracks how adapted the athlete currently is to training in heat
    and at altitude. heat_acclimation_percent runs 0-100 and decays without
    continued exposure; use it to judge readiness for a warm-weather race.

    heat_trend reports Garmin's own label (e.g. ACCLIMATIZED). The
    previous_* fields hold the prior reading so direction of travel is
    visible without a second call.

    VO2 max is not returned here; use get_training_status or get_vo2max_trend.

    Args:
        date: Date in YYYY-MM-DD format
    

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_acclimation"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuine semantics beyond that, explaining the 0-100 scale of heat_acclimation_percent, that it decays without continued exposure, what heat_trend's label means, and that previous_* fields expose direction of travel. That is valuable given no output schema exists. It stops short of describing altitude fields with the same precision and says nothing about behavior when no acclimation data exists for the requested date.

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?

Front-loads the core purpose in the first line, then spends the body on field semantics, the decay caveat, and the alternative routing. The Args block is minimal boilerplate but is the only structured place for the format detail, so it earns its line.

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, the description must carry return-value meaning and it largely does, covering the percent scale, trend label, and prior-reading fields. A mutation-free read tool with one parameter needs little more, though a note on what is returned when no heat or altitude exposure is recorded would close the remaining gap.

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 coverage is 0% and the schema documents nothing about the single date parameter beyond type string, so the description's "Date in YYYY-MM-DD format" is load-bearing rather than redundant. It could go further on timezone/current-day semantics for a status that decays, but the essential format is supplied.

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 ("Get heat and altitude acclimation status for a given date") and scopes it by date. It also explicitly excludes related data ("VO2 max is not returned here") and names the siblings that do hold it, letting an agent distinguish it from get_training_status and get_vo2max_trend without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit decision rule for consumption ("use it to judge readiness for a warm-weather race") and an explicit routing rule for the data it does not cover ("use get_training_status or get_vo2max_trend"). Both when-to-use and when-not-to-use are present, which is more than most definitions provide.

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