Skip to main content
Glama

getActivity

Read-only

Retrieve full JSON details for a single Garmin activity, including summary metrics, split summaries, activity type, and device metadata, when list activities lacks the fields you need.

Instructions

Garmin's full JSON for one activity: summaryDTO (start time, distance in metres, duration and movingDuration in seconds, averageSpeed in m/s, HR, calories, training effect and load, intensity minutes, Body Battery change, sets and reps of a strength session), splitSummaries (one total per split type, such as the run and walk segments), the activity type and metadataDTO (device maker, lap count, personal record flag). Private ids are left out. Use it for a field that listActivities does not give: listActivities gives the common fields in km and min/km, for many activities in one call. It has no laps, sets or samples: use getActivityLaps, getActivitySets or downloadActivityFit for them.

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": {
      "activityId": "<activityId>"
    },
    "name": "getActivity"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityIdYesGarmin activity id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply readOnlyHint and openWorldHint; the description adds substantive behavior beyond them: the exact units of each returned field, that private ids are omitted, and an explicit statement of what is absent (no laps, sets or samples). For a read tool with no output schema, this is unusually complete disclosure of the response shape.

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?

Front-loaded with the core purpose, then payload contents, then the routing to alternatives — a sensible order. The long parenthetical field inventory is dense but each item conveys return-value meaning that has no output schema to carry it, so little is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of describing return values and does so field-by-field with units, plus guidance on which sibling to use for omitted data. Nothing an agent needs to call it correctly or interpret the response appears to be missing.

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?

The single parameter activityId is fully described in the schema ('Garmin activity id'), and the description adds no further syntax, format, or sourcing guidance for it. With 100% schema coverage the baseline of 3 applies.

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?

Names a specific verb+resource ('Garmin's full JSON for one activity') and enumerates the exact payload blocks returned (summaryDTO, splitSummaries, activity type, metadataDTO). The parenthetical field list with units makes it unmistakable versus listActivities, which returns only common fields.

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?

Explicitly states when to use it — 'for a field that listActivities does not give' — and contrasts what listActivities returns instead (km, min/km, many activities per call). It also routes the agent away for sibling concerns, naming getActivityLaps, getActivitySets and downloadActivityFit for laps, sets and samples.

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