Skip to main content
Glama
Sign In
Garmin MCP Server

Garmin MCP Server

by JJRPF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_activity_exercise_sets

Retrieve exercise-by-exercise set details for a strength training activity using its ID to review reps, weight, and performance per set.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'Get' implies a read-only operation, which is appropriate, but it does not specify what happens for non-strength activities, whether an empty result is possible, or any error behavior.

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 description is concise and front-loaded with the main purpose. The Args section is slightly redundant with the schema, but it is not bloated or confusing.

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 getter with an output schema, the basics are covered: what the tool retrieves and which parameter to pass. However, it lacks any context about activity type expectations, empty results, or relationship to similar tools, leaving some ambiguity for an agent.

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 must compensate. It does explain that activity_id is the ID of the activity to retrieve sets for, but this adds only modest meaning beyond the parameter name and schema type.

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 clearly states a specific verb and resource: 'Get exercise sets for strength training activities.' It does not explicitly compare against siblings, but the resource is distinct enough that an agent can infer what this tool does.

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?

The phrase 'for strength training activities' implies the intended use case, but the description gives no explicit guidance on when to choose this over related activity data tools like get_activity_splits or get_activity_fit_data, and no exclusions are provided.

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