Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_activities

Read-only

Retrieve a paginated list of Garmin Connect activities, newest first, and filter by activity type or subtype to review recent workouts.

Instructions

Return a page of activities, newest first, optionally filtered by type. :param start: Starting activity offset, where 0 means the most recent activity :param limit: Number of activities to return :param activitytype: (Optional) Filter activities by type :param activitysubtype: (Optional) Filter activities further by sub-type. :return: List of activities from Garmin. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
activitytypeNo
activitysubtypeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond annotations: results are newest first, 'start' is an offset where 0 means the most recent activity, and the source is Garmin Connect. It does not discuss rate limits, authentication, or maximum page size, but those are secondary here.

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?

The main purpose is front-loaded in the first sentence, and the docstring-style parameter block is compact and useful given the empty schema descriptions. The final note about dates being YYYY-MM-DD is slightly extraneous for a tool whose parameters contain no dates, but it does not materially bloat the definition.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers ordering, pagination, all parameters, and the return context, and an output schema exists. However, in a dense family of activity-related tools, it lacks the selection context needed to distinguish this general paged listing from get_activities_by_date, count_activities, get_last_activity, and get_activity.

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 carry the parameter semantics, and it does document all four parameters. The explanation of 'start' as an offset where 0 means the most recent activity is especially valuable, though 'activitytype' and 'activitysubtype' only restate their names rather than listing accepted values or formats.

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 states a specific verb and resource: it returns a page of activities, newest first, optionally filtered by type. That is clear enough to understand the tool's purpose, but it does not explicitly distinguish it from siblings such as get_activities_by_date, get_last_activity, or count_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 phrase 'optionally filtered by type' implies when the type filters apply, and the pagination semantics imply how to page through results. However, it gives no explicit when-not-to-use guidance and does not name alternatives for date-based filtering, latest-activity lookup, or activity details.

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