Garmin MCP Server

Overview Schema Source Related Servers Discussions Admin

get_activity_gear

Retrieve gear data associated with an activity by passing its activity ID. Find out which equipment was used for any recorded workout.

Instructions

Get gear data used for an activity

Args: activity_id: ID of the activity to retrieve gear data 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_gear"
  }
}

Input Schema

Name	Required	Description	Default
`activity_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The name and description imply a read-only operation, but no explicit statement about side effects or lack thereof is made. Since annotations are absent, the description carries the full burden; it does not clarify whether the returned gear data includes all fields or just summaries, nor does it mention any rate limits or authentication requirements.

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?

The description is extremely concise, consisting of one clear sentence plus the parameter explanation. No unnecessary words or redundant information is present.

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 simple retrieval tool, the description is adequate. It does not cover return value details or error conditions, but since an output schema exists (as indicated by context), the lack of return-value explanation is acceptable. The description covers the essential purpose and parameter.

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 description explicitly explains the sole parameter: 'ID of the activity to retrieve gear data for'. This provides clear meaning for activity_id. However, it does not specify whether the ID is numeric or string-based, which could cause minor ambiguity given the anyOf type in the schema.

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?

The description clearly states the action: 'Get gear data used for an activity' and identifies the specific resource (gear for an activity). This verb+resource combination is unambiguous and distinct from sibling tools like get_gear or add_gear_to_activity.

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?

No guidance is provided on when to use this tool versus alternatives such as get_gear (list all gear) or add/remove gear tools. The description does not mention any conditions, prerequisites, or scenarios that would make this tool the preferred choice.

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

Deploy Server