Skip to main content
Glama

get_workouts

Read-only

Retrieve a count and curated summary list of Garmin Connect workouts with essential metadata. Use detailed workout lookup for segments or full workout information.

Instructions

Get all workouts with curated summary list

    Returns a count and list of workout summaries with essential metadata only.
    For detailed workout information including segments, use get_workout_by_id.
    

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_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 description is not needed for safety framing. It does add value beyond them by describing the return payload ('count and list of workout summaries with essential metadata only'), which matters since no output schema exists. It omits whether results are paginated, capped, or ordered despite claiming 'all workouts'.

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?

Three short lines, with the scope and result shape front-loaded before the alternative-tool pointer. No filler or restated name/title.

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 no-parameter read tool the description covers purpose, result shape, and the detail-vs-summary tradeoff. The remaining gap is scale behavior (pagination/limits on returning 'all' workouts), which matters for an open-world read but is a minor omission.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No misleading parameter language is present.

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 ('Get all workouts') plus the shape of the result ('curated summary list'), and explicitly distinguishes itself from get_workout_by_id, which returns detail. An agent can tell the two apart without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to get_workout_by_id when detailed data such as segments is needed, which is a clear use/don't-use split for the main confusable sibling. It does not address the other workout-listing siblings, but those are not named in the definition and their behavior is not inferable.

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