Skip to main content
Glama

get_calendar_events

Read-only

Retrieve races and events from your Garmin Connect calendar between two dates to answer questions about scheduled races, event distances, goal times, and primary goal races.

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 distance in meters when Garmin stores one,
    the user's custom goal time in seconds when set, 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. Goal time
    comes from a per-event detail request.

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

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), but the description adds real behavioral context beyond them: it enumerates the returned fields (distance in meters, goal time in seconds, local start time, is_race, primary_event) and warns that goal time requires a separate per-event detail request, which hints at extra latency. It stops short of stating auth requirements or empty-range behavior, so it is not fully complete, but it is well above the annotation baseline.

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?

Front-loaded with purpose, then disambiguation, then return semantics, then args, which is a sensible ordering. The paragraph on returned fields is dense but earns its place given the absence of an output schema; the 'This is the only tool that exposes them' line slightly repeats the preceding sentence.

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?

There is no output schema, so the description carries the burden of describing return values and does so field by field, including the meaning of the is_race and primary_event flags. Combined with the sibling exclusion and date format note, an agent has enough to call it and interpret results correctly.

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% and the schema only supplies titles ('Start Date', 'End Date'), so the description's YYYY-MM-DD format note and 'between two dates' framing genuinely compensate for part of the gap. However, it never states whether the end date is inclusive, whether dates are interpreted in local or UTC time, or what happens with an inverted range, leaving real ambiguity for a ranged query.

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?

States a specific verb and resource with scope: 'Get races and events on the Garmin Connect calendar between two dates.' It goes further to name the two sibling tools it is not (get_scheduled_workouts, get_goals) and asserts it is the only tool exposing these entries, so an agent can disambiguate without opening any schema.

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?

Gives explicit when-to-use guidance ('Use this to answer questions about which events or races are scheduled') and explicit exclusion criteria by naming get_scheduled_workouts as workouts-only and get_goals as a separate concern. Both the positive trigger and the alternatives are spelled out.

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