Skip to main content
Glama
Sign In
Garmin Connect MCP Server

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Compare Activities

compare_activities
Read-only

Compare 2-5 Garmin activities side-by-side to analyze distance, duration, speed, heart rate, calories, elevation, steps, and training effect.

Instructions

Compare 2-5 activities side by side: distance, duration, speed, heart rate, calories, elevation, steps and training effect.

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": {
      "activityIds": "<activityIds>"
    },
    "name": "compare_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityIdsYesArray of 2-5 activity IDs to compare (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the tool read-only, so the safety profile is covered. The description adds useful context about the comparison (side-by-side fields), but it does not disclose return format, error behavior, or any limits beyond the schema-provided range.

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 a single front-loaded sentence that states the action, the count range, and the compared metrics with no filler or repetition. Every phrase earns its place.

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, read-only comparison tool with one well-documented parameter, the description is largely sufficient. It lacks an explicit output/return description, but 'side by side' plus the listed metrics makes the result reasonably predictable.

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 coverage is 100%: activityIds is already described as an array of 2-5 activity IDs. The description reinforces the range but adds no new semantic information about parameter format or ID source beyond the schema.

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?

Description uses a specific verb ('Compare') with a clear resource ('2-5 activities') and enumerates the metrics involved. This distinguishes it from single-activity tools like get_activity_details and similarity tools like find_similar_activities.

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 clearly implies usage: compare a set of 2-5 activities. However, it does not explicitly state when to prefer this over alternatives such as get_activity_details or analyze_training_period, nor does it mention exclusions.

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