Skip to main content
Glama

get_activity_exercise_sets

Read-only

Retrieve exercise sets for a specific strength training activity by providing its activity ID. Use it to review set-level workout details from Garmin Connect.

Instructions

Get exercise sets for strength training activities

    Args:
        activity_id: ID of the activity to retrieve exercise sets for
    

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

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 safety profile is covered without the description's help. The description adds only the strength-training scoping; it says nothing about whether an empty set is returned for non-strength activities, whether results are paginated, or how sets are ordered. For a read tool with annotation coverage this is thin but not misleading.

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?

The purpose sentence is front-loaded and wastes no words. The trailing 'Args:' block largely duplicates the schema and the parameter name, so it is minor filler rather than useful structure.

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?

For a one-parameter read tool with annotations and no output schema, the definition is minimally sufficient to invoke correctly. It is incomplete about what an 'exercise set' contains and about behavior for activities without strength data, which an agent would need to interpret results.

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 0%, so the description carries the burden for the single activity_id parameter, and it does restate that it identifies the activity whose exercise sets are retrieved. However, it adds no format guidance despite the schema accepting either integer or string, and no detail on how the ID is obtained.

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 verb and resource ('Get exercise sets') and narrows scope to strength training activities, which is enough for an agent to tell it apart from activity-summary siblings like get_activity or get_activity_splits. It stops short of naming its write counterpart set_activity_exercise_sets explicitly, so sibling differentiation is implied rather than stated.

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 when-to-use guidance, no mention of prerequisites (e.g. the activity must be a strength workout), and no routing to alternatives such as get_activity or set_activity_exercise_sets. The 'strength training' qualifier hints at applicability but never states what happens for non-strength activities.

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