Garmin MCP Lite

Overview Schema Source Related Servers Discussions Admin

garmin_add_event

Add races or events to Garmin Connect with date, distance, goal time, location, and notes so athletes can plan and track key target events.

Instructions

Add a calendar race or event to Garmin Connect.

Args: name: Event name (required). date: Event date in YYYY-MM-DD format (required). distance_km: Event distance in kilometers (e.g. 21.0975 for half marathon, 42.195 for marathon). goal_time: Target finish time in H:MM:SS or MM:SS format (e.g. "1:32:05", "3:00:00"). is_race: Whether this event is a race (defaults to True). is_primary: Whether this is the primary focus event in Garmin (defaults to False). event_type: Sport type (defaults to "running"). start_time: Start time in HH:MM format (optional). time_zone_id: Timezone string if start_time is given (defaults to "Asia/Shanghai"). location: City or venue location name (optional). note: Description or note (optional).

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": {
      "name": "<name>",
      "date": "<date>"
    },
    "name": "garmin_add_event"
  }
}

Input Schema

Name	Required	Default
`date`	Yes
`name`	Yes
`note`	No
`is_race`	No
`location`	No
`goal_time`	No
`event_type`	No	running
`is_primary`	No
`start_time`	No
`distance_km`	No
`time_zone_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.10Nov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden for a write operation. It usefully gives formats and default values for most fields, but is silent on what happens with duplicate events on the same date, whether the call fails or overwrites, and what permissions or auth are needed. Because an output schema exists, the absent return-value description is a minor gap rather than a major one.

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?

One-line purpose followed by a compact Args block with no filler; the required/optional markings are front-loaded per parameter. The format is docstring-derived, so some lines repeat defaults already visible in the schema, but nothing is wasted enough to hurt readability.

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 an 11-parameter mutation tool with only 2 required fields, the description covers every input and its format, and the output schema handles return values. What is missing is failure/duplicate behavior and the timezone-default discrepancy, which matter for correct invocation but are secondary to the input documentation.

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?

With 0% schema description coverage, the description has to carry every field, and it does: all 11 parameters are named with meaning, format, and concrete examples ("21.0975 for half marathon", "1:32:05"). It loses a point because it restates schema defaults (is_race, is_primary, event_type) and because time_zone_id is described as defaulting to "Asia/Shanghai" while the schema declares default null, a real inconsistency an agent could trip on.

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?

The first sentence gives a specific verb and resource: 'Add a calendar race or event to Garmin Connect.' That is enough to separate it from the read-only siblings (garmin_events, garmin_activity_detail) and from garmin_delete_event. It never names an alternative or notes the boundary, so it stops short of a 5.

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?

The description only states what the tool does, not when to use it. There is no guidance on when to add a calendar event rather than use garmin_schedule_running_workout or garmin_training_plan, and no prerequisites such as the Connect account or device sync being required for the event to appear. An agent has to guess the intended scenario.

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