Skip to main content
Glama

get_activity

Read-only

Retrieve detailed data for a single Garmin Connect activity by ID, including timing, distance, heart rate, elevation, training effect, and event type, to review or analyze that workout.

Instructions

Get detailed information for a single activity.

    Returns a comprehensive summary including timing, distance, heart rate,
    elevation, training effect, and an event_type field. Common event_type
    values: "race", "training", "uncategorized" (no event type set by the
    user). The field is omitted when Garmin returns no eventTypeDTO.

    Args:
        activity_id: ID of the activity to retrieve
    

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds real value beyond that by enumerating the returned summary fields (timing, distance, heart rate, elevation, training effect) and documenting a conditional omission rule for event_type when Garmin returns no eventTypeDTO.

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?

Well front-loaded: the one-line purpose comes first, followed by return-value detail, then the argument. The 'Args:' block largely repeats the schema and is slight padding, but nothing else is 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?

For a one-parameter read tool with no output schema, the description supplies the key missing piece — what the response contains — plus the notable event_type omission behavior. Combined with the annotations, an agent has enough to call it correctly.

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%, so the description carries the burden, and it only says 'activity_id: ID of the activity to retrieve' — a near restatement of the parameter name. It does not mention that the schema accepts either an integer or a string, nor where an agent would obtain the ID.

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 opens with a specific verb+resource: 'Get detailed information for a single activity,' which cleanly separates it from plural listing tools like get_activities. It does not, however, explicitly name the many sibling sub-resource tools (get_activity_splits, get_activity_fit_data) to say what this one is not.

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 scope phrase 'single activity' implies this is the general summary lookup rather than the splits/FIT/weather sub-resource tools, but usage is only implied. There is no explicit when-to-use or when-to-prefer-a-sibling guidance, and no stated prerequisites.

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