Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_activity

Read-only

Retrieve detailed summary metrics for a single Garmin Connect activity by ID, including distance, duration, heart rate, calories, training load, steps, type, time zone, and device.

Instructions

Details of one activity: summary (distance, durations, speed, heart rate, calories, training effect and load, intensity minutes, steps), type, time zone and device.

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

Input Schema

NameRequiredDescriptionDefault
activity_idYesActivity ID from search_activities (a positive integer).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no further behavioral context — no note on behavior for an invalid or unknown activity_id, no rate limits, no auth requirements.

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?

One front-loaded sentence with no filler; the parenthetical list is dense but each item conveys what the caller can expect. Slightly list-heavy, but nothing is wasted.

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?

An output schema exists, so the field enumeration is somewhat redundant, and the remaining needs for a single-parameter read tool (ID semantics, read-only nature) are covered by schema and annotations. Adequate overall.

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 100% and the single activity_id parameter is already documented in the schema as a positive integer sourced from search_activities. The description adds nothing beyond that, so the baseline of 3 applies.

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 resource (one activity) and enumerates the contents returned: summary metrics, type, time zone and device. That enumeration implicitly separates it from siblings like get_activity_laps or get_activity_splits, though no sibling is named explicitly, so it falls short of full differentiation.

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 phrase "Details of one activity" implies the use case (fetch a single activity by ID), and the schema points to search_activities as the ID source. There is no explicit when-to-use vs. when-not guidance or mention of alternatives such as get_activity_laps when lap-level data is needed.

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