Skip to main content
Glama
garmin-personal-api-mcp

garmin-personal-api-mcp

by aaronhaddad

Wellness activities

garmin_get_wellness_activities
Read-onlyIdempotent

Fetch wellness activity summaries, including breathwork and relaxation sessions, for a date range; long ranges are automatically retrieved in chunks up to 366 days.

Instructions

Wellness activity summaries (e.g. breathwork and relaxation sessions) for the range.

Long ranges are fetched in chunks automatically (up to 366 days).

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

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast day, inclusive. Defaults to today. Same formats as start_date
start_dateYesFirst day, inclusive: YYYY-MM-DD, "today", "yesterday" or "N days ago"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive safety. The description adds real value beyond them: automatic chunked fetching and a 366-day cap, which tells the agent how long-range calls behave. Return shape is unspecified, keeping 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 tight sentences, purpose front-loaded, with the chunking caveat second. No filler.

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 two-parameter read with full schema coverage and complete safety annotations, the description gives everything needed to call it correctly. Only the return payload shape is left implicit, which is minor given no output schema.

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%, so both start_date and end_date formats/defaults are fully documented in the schema. The description only alludes to a 'range' without adding syntax beyond that; baseline 3 fits.

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?

States a specific resource ('Wellness activity summaries') with concrete examples (breathwork, relaxation sessions) and scope ('for the range'). This distinguishes it reasonably well from step/sleep/stress siblings, though it doesn't explicitly name a contrasting sibling.

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?

Usage is only implied via 'for the range'; there is no statement of when to prefer this over garmin_get_day or garmin_get_daily_summaries. The chunking note is helpful operational context but not selection guidance.

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