Skip to main content
Glama

get_activity_weather

Read-only

Fetch weather data for a Garmin activity by ID, converting temperatures to the account’s display unit (C or F) and labeling wind speed in its returned unit.

Instructions

Get weather data for an activity.

    Garmin's weather endpoint returns temperatures in Fahrenheit (from the
    weather-station source) with no unit indicator, regardless of account
    settings. This tool converts them to the account's display unit: metric
    accounts get Celsius, statute_us accounts keep Fahrenheit. The
    temperature_unit field ("F" or "C") states which unit was returned.

    Wind speed, unlike temperature, is already returned in the account's
    display unit (km/h for metric, mph for statute_us), so it is passed
    through unconverted and labeled via the wind_speed_unit field.

    Args:
        activity_id: ID of the activity to retrieve weather data for
    

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior5/5

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

Annotations already cover the read-only, non-destructive, open-world profile, and the description goes substantially beyond them: it discloses a Garmin endpoint quirk (Fahrenheit with no unit indicator regardless of account settings), the conversion rule per account type, and the presence of temperature_unit and wind_speed_unit labels in the response. It even explains why wind speed is treated differently from temperature, which an agent could not infer from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded correctly, but three paragraphs of unit-plumbing detail for a single-parameter getter is disproportionate, and the Args block adds nothing the schema does not already show. The unit information is genuinely useful given the absent output schema, so it earns some of its space, but it could be compressed.

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 with annotations and no output schema, the description covers the non-obvious parts: return units, unit labels, and the asymmetry between temperature and wind speed. It leaves out failure modes such as activities with no weather data, which is the main remaining gap.

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 description coverage is 0%, but there is only one parameter and the schema's anyOf (integer or string) is largely self-explanatory. The Args section merely restates the property title ('ID of the activity to retrieve weather data for') without noting format, whether IDs are accepted as strings from other tools' output, or any validation behavior, so it adds little.

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 first sentence states a specific verb and resource ('Get weather data for an activity') that clearly separates it from the surrounding get_activity_* data tools. It does not explicitly name or rule out any sibling, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of what happens for activities without weather-station coverage. The only implied guidance is the obvious 'use it to get weather for an activity', which restates the purpose.

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