garmin-mcp

get_activity_weather

Retrieve weather conditions recorded during a Garmin activity, including temperature, humidity, and wind, by providing the activity's numeric ID.

Instructions

Weather conditions recorded during an activity (temp, humidity, wind).

Units follow your Garmin account's measurement system (US accounts report degrees Fahrenheit and mph).

Args: activity_id: The activity's numeric Garmin ID, from get_recent_activities.

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

Name	Required	Description	Default
`activity_id`	Yes

Output Schema

Name	Required	Description
`note`	No
`temp`	No
`dew_point`	No
`wind_gust`	No
`wind_speed`	No
`activity_id`	Yes
`description`	No	e.g. Fair, Cloudy, Rain.
`observed_at`	No
`station_name`	No
`apparent_temp`	No
`relative_humidity`	No
`wind_direction_compass`	No
`wind_direction_degrees`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that units follow the Garmin account's measurement system, which is useful behavioral context. However, it doesn't mention any side effects (likely none for a read operation), error conditions, or what happens if the activity has no weather data. The description adds some value but lacks depth.

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 concise and well-structured. It starts with a clear one-sentence summary, then provides a note about units, and finally documents the parameter. Every sentence adds value, and it's appropriately sized for a simple tool with one parameter.

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?

Given the tool's simplicity (one parameter, no annotations, output schema exists), the description is fairly complete. It explains the data returned (temp, humidity, wind) and the unit system. It doesn't detail the output structure, but the output schema likely covers that. The only gap is not mentioning what happens if no weather data is available, but that's minor.

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 compensate. It explains that activity_id is the numeric Garmin ID and references get_recent_activities for obtaining it, which adds meaning beyond the schema's bare type definition. This is helpful for the agent to know how to source the parameter.

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 states the tool retrieves weather conditions recorded during an activity, listing specific data types (temp, humidity, wind). It distinguishes from siblings by focusing on weather data, which is unique among the listed tools. However, it doesn't explicitly contrast with any sibling, so it's clear but not fully differentiated.

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?

The description implies usage by requiring an activity_id from get_recent_activities, which provides context on when to use it (after fetching activities). It doesn't explicitly state when not to use it or mention alternatives, but the dependency on get_recent_activities gives some guidance. No explicit exclusions or alternative tools are mentioned.

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

Deploy Server