Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by saryva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_activities

Retrieve recent Garmin Connect activities with distance, duration, average heart rate, and elevation. Filter by activity type like running or cycling.

Instructions

Lista actividades/entrenamientos recientes de Garmin Connect, con distancia, duración, frecuencia cardíaca media y desnivel. Usa activity_type (p. ej. 'running', 'cycling') para filtrar por deporte.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
activity_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose whether authentication is needed, pagination behavior, ordering, or data freshness. These gaps limit an AI agent's ability to invoke correctly.

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?

Two sentences, no extraneous text. Front-loaded with purpose, immediately actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite low complexity (3 params, no nested objects), the description omits critical context: authentication, return format, pagination, error handling. Inadequate for a tool with no output schema or annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must explain all parameters. It explains activity_type but not limit and start, leaving basic pagination semantics undocumented.

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?

Description clearly states it lists recent activities from Garmin Connect, specifying included fields (distance, duration, heart rate, elevation). It implies differentiation from sibling tools (e.g., get_activity_detail) but could explicitly contrast list vs detail.

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?

Provides guidance on using activity_type parameter for filtering but lacks explicit when-to-use or when-not-to-use instructions relative to siblings or prerequisites.

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