Skip to main content
Glama

create_manual_activity

Log a manual activity in Garmin Connect for workouts done without a watch, using activity type, date, duration, and optional start time, distance, and time zone.

Instructions

Log a manual activity in Garmin Connect — useful for activities done without a watch.

    The type_key must match a Garmin activity type. Use get_activity_types to see
    the full list. Common values: yoga, strength_training, meditation, indoor_cycling,
    pilates, bouldering, fitness_equipment.

    Args:
        type_key: Activity type key (e.g. "yoga", "strength_training")
        date: Date of the activity in YYYY-MM-DD format
        duration_minutes: Duration of the activity in minutes
        start_time: Start time as HH:MM (24-hour, default 09:00)
        activity_name: Optional title; defaults to the type_key if not provided
        distance_km: Distance in kilometres (default 0.0 for non-distance activities)
        time_zone: IANA time zone for the activity (default UTC)

    If a write fails with write_committed="unknown", check whether the
    activity exists before retrying to avoid creating a duplicate.
    

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": {
      "type_key": "<type_key>",
      "date": "<date>",
      "duration_minutes": "<duration_minutes>"
    },
    "name": "create_manual_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
type_keyYes
time_zoneNoUTC
start_timeNo09:00
distance_kmNo
activity_nameNo
duration_minutesYes

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 declare a non-read-only, non-idempotent, open-world write. The description adds real value beyond them by warning about duplicate creation when write_committed="unknown" and telling the agent to check existence before retrying — a concrete, non-obvious behavioral trait. It does not cover permissions/auth or what the call returns, which are the remaining gaps.

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 purpose and the type_key routing are front-loaded, then parameters, then the retry hazard — a sensible order. The Args block repeats defaults (UTC, 09:00, 0.0) that are already in the schema, which is mild redundancy but useful for scanability.

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 7-parameter, non-idempotent mutation with no output schema, the definition covers purpose, valid type keys, parameter formats, and duplicate-creation risk, which is close to what an agent needs. Gaining a 5 would require stating auth/permission requirements or the shape of the success response.

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?

Schema coverage is 0%, so the description must carry the load, and it does: all seven parameters are documented with formats (YYYY-MM-DD, HH:MM 24-hour, IANA time zone), a domain constraint (type_key must match a Garmin type plus seven concrete examples), and defaulting behavior for activity_name and distance_km.

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 opens with a specific verb and resource ('Log a manual activity in Garmin Connect') and immediately narrows the scope with 'useful for activities done without a watch', which distinguishes it from watch-recorded or workout-creation siblings like create_run_workout.

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

Usage Guidelines4/5

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

It gives a clear trigger context (activities recorded without a device) and explicitly routes the agent to get_activity_types for valid type_key values, which is the main prerequisite. It stops short of stating when NOT to use it (e.g. for device-recorded activities) in explicit negative form, but the 'without a watch' framing implies the boundary.

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