Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

search_activities

Read-only

Search recorded Garmin Connect activities by date range or activity type to retrieve paginated stats including distance, duration, heart rate, training load, and time in HR zones.

Instructions

Recorded activities, newest first: name, type, start time, distance (m), duration (s), speed (m/s), calories, average/max HR, aerobic and anaerobic training effect, training load, seconds in HR zones 1-5, intensity minutes, Body Battery change and strength sets.

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": "search_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax activities to return.
startNoOffset for paging, newest first.
end_dateNoOnly activities on or before this date (YYYY-MM-DD).
start_dateNoOnly activities on or after this date (YYYY-MM-DD).
activity_typeNoGarmin type key, e.g. running, cycling, strength_training.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds only the 'newest first' ordering behavior; it does not mention pagination behavior, filtering semantics, or any operational constraints beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is not front-loaded with a clear purpose and spends most of its length enumerating return fields that are already covered by the output schema. It is concise in word count but poorly structured for an agent deciding whether and how to call the tool.

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

Completeness2/5

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

Because an output schema exists, the description does not need to list return fields, yet that is almost all it does. It omits the search/filter context (date range, activity type, paging) that would help an agent use this list tool correctly relative to its siblings.

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%, and all five parameters have clear descriptions in the schema. The description adds no parameter meaning at all, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as recorded activities and notes ordering (newest first), but it never explicitly states the action (list/search/filter) and does not distinguish this tool from siblings such as get_activity. The sentence is dominated by a return-field inventory rather than a clear purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus get_activity or the other activity-specific tools, nor any mention of using date/type filters. The agent must infer usage entirely from the tool name and schema.

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