Garmin MCP

garmin_activity_types

Get a complete list of Garmin activity types with their IDs and keys to identify supported activities for data queries and analysis.

Instructions

List all Garmin activity types (running, cycling, strength_training, etc.) with type IDs and keys.

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": "garmin_activity_types"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are present, so the description carries the full disclosure burden. It correctly conveys a read-only catalog enumeration, which is self-evident from 'List all ... with type IDs and keys.' However, it doesn't disclose whether authentication is required or describe any limits or output shape beyond the fields mentioned — adequate for a simple lookup but not rich.

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?

A single front-loaded sentence that names the verb, resource, examples, and output fields with zero filler. Every clause earns its place.

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 zero-parameter catalog lookup, the description combined with the existing output schema is nearly complete. The only notable gap is the absence of any statement about auth or session requirements on a tool that sits alongside garmin_login, but this is a minor omission for such a simple operation.

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 has zero parameters and 100% schema coverage, so the baseline is 4. The description adds value by specifying what returned entries contain (type IDs and keys), which orients the agent even though there is nothing to configure on input.

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 ('List'), a clear resource ('Garmin activity types'), and the expected output fields (type IDs and keys). The examples (running, cycling, strength_training) make the scope self-evident. It doesn't explicitly disambiguate from siblings like garmin_activities or garmin_activity_details, but the catalog-vs-records distinction is implicit in 'activity types ... with type IDs and keys.'

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 on when to use this lookup versus sibling tools such as garmin_activities (the user's actual activity log) or garmin_activity_details. No mention of prerequisites such as login, even though a garmin_login sibling exists.

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

Deploy Server