Garmin MCP Server

Overview Schema Source Related Servers Discussions Admin

get_calendar_events

Retrieve races and events scheduled in Garmin Connect between two dates, including target distance, start time, and race flags.

Instructions

Get races and events on the Garmin Connect calendar between two dates

Returns calendar entries the user added or subscribed to in Garmin Connect, such as upcoming races. Use this to answer questions about which events or races are scheduled.

These entries are not returned by get_scheduled_workouts, which covers only workouts, nor by get_goals. This is the only tool that exposes them.

Each event reports its target distance in meters when Garmin stores one, the local start time when the organiser published it, and two flags: is_race marks the entry as a race rather than a general event, and primary_event marks the goal race that an active training plan targets.

Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end_date`	Yes
`start_date`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses that it returns user-added or subscribed entries, includes target distance in meters when available, local start time when published, and two flags. It does not explicitly state it is read-only, but the nature of a getter is implied, and it does not hide any side effects.

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 well-structured with a clear purpose statement, a detail paragraph, and an args section. It is slightly repetitive (the first sentence and the second paragraph both describe what is returned), but the repetition reinforces the key points without being verbose.

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

Completeness5/5

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

Given the low complexity (2 simple parameters and an output schema), the description covers all necessary context: what the tool returns, parameter formats, and its unique role among siblings. It does not need to explain output schema details since an output schema exists.

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

Parameters5/5

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

The schema has zero description coverage, so the description must compensate. It does so by specifying 'Start date in YYYY-MM-DD format' and 'End date in YYYY-MM-DD format' for both parameters, providing essential format guidance beyond the bare 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 verb 'Get' with the resource 'calendar events' and the scope 'between dates'. It also explicitly differentiates from sibling tools by noting that scheduled workouts and goals do not cover these entries, making it unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: it is the only tool that returns calendar entries such as races and events, and it contrasts with get_scheduled_workouts and get_goals. This clarifies the selection criteria among alternatives.

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

Deploy Server