Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_activity_workouts

Read-only

Retrieve the planned workout steps and targets recorded against a Garmin activity to compare intended structure with actual performance.

Instructions

The planned workout (steps and targets) the activity was recorded against, if any.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYesActivity ID from search_activities (a positive integer).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 the safety profile is covered. The description usefully adds that the result is conditional ('if any'), signaling a possible null return, but says nothing about what 'steps and targets' contain beyond the hint, and an output schema carries the return shape.

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?

A single short sentence with no wasted words; the parenthetical adds clarifying content about what 'workout' means. It is front-loaded and readable, though it is a sentence fragment whose brevity borders on under-specification rather than efficiency.

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?

An output schema exists, so return-value explanation is not required, and the one parameter is fully documented. The remaining gap is guidance on when this tool should be chosen over sibling activity endpoints, which leaves the definition minimally viable rather than complete.

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 the single activity_id parameter is documented in the schema with its provenance (from search_activities) and positivity constraint. The description adds no additional meaning about the parameter, so the baseline 3 applies.

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 names a specific resource — the planned workout (steps and targets) an activity was recorded against — which is clearly distinct from siblings like get_activity or get_activity_laps. It reads as a noun phrase describing the payload rather than an explicit verb+resource statement, but an agent can still tell exactly what it returns.

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 explicit when-to-use guidance, no mention of prerequisites, and no routing to an alternative such as the broader get_activity or search_activities. The only contextual cue is the trailing 'if any', which hints the result may be absent but does not tell the agent when to prefer this tool.

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