Skip to main content
Glama
garmin-connect-mcp

garmin-connect-mcp

by Samiu1

Get Wellness Activities

garmin_get_wellness_activities
Read-onlyIdempotent

List automatically detected wellness activities over a date range to review low-effort movement Garmin logs without started workouts, separate from recorded workouts.

Instructions

List automatically detected wellness activities over a date range: the low-effort movement Garmin logs without the user starting a workout, such as walks.

These are distinct from recorded workouts; use garmin_search_activities for those. Each entry includes the device that recorded it.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "garmin_get_wellness_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesLast date in range, inclusive, YYYY-MM-DD
start_dateYesFirst date in range, inclusive, YYYY-MM-DD
response_formatNo'markdown' for readable text, 'json' for the exact Garmin field names and valuesmarkdown
include_empty_fieldsNoKeep fields Garmin returned as null or empty. Off by default, since unsupported sensors on the user's device produce large runs of nulls. Turn on only to inspect raw shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: these are device-inferred entries rather than user-initiated records, which explains their data quirks, and it discloses that each entry carries the recording device. It does not touch pagination, ordering, or result-size limits, which keeps it short of a 5.

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?

Two short sentences, front-loaded with the definition, followed by the disambiguation and a one-clause return note. No hedging, no repetition of the title, nothing that could be cut without losing guidance.

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?

With no output schema and only four simple parameters, the description needs to cover what the entries are and roughly what comes back; it does both (auto-detected movement plus recording device). It stops short of describing result shape or ordering, but for a read-only list tool with fully documented params that gap is minor.

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%, including date format patterns and the meaning of response_format and include_empty_fields, so the schema does the heavy lifting. The description only implies date-range filtering and adds nothing about the parameters beyond that. Baseline 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?

States a specific verb and resource ("List automatically detected wellness activities over a date range") and disambiguates the concept in plain language: "the low-effort movement Garmin logs without the user starting a workout, such as walks." It also names the sibling it is not to be confused with, so an agent can differentiate it without opening any schema.

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?

Gives an explicit alternative with the selecting condition: "These are distinct from recorded workouts; use garmin_search_activities for those." The date-range scoping in the first line further tells the agent what input shape is expected, leaving no inference required about which tool handles user-started workouts.

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