Skip to main content
Glama

set_activity_type

Destructive

Change an activity's sport type to correct mislabelled Garmin activities, such as switching a trail run to running or a treadmill walk to treadmill walking.

Instructions

Change the activity type (sport) of an activity.

    Useful for reclassifying a mislabelled activity, e.g. flipping a run
    logged as 'trail_running' to 'running', or a 'treadmill_running' walk to
    'treadmill_walking'. Call get_activity_types to see all valid type keys.

    Args:
        activity_id: ID of the activity to update
        type_key: Target activity type key (e.g. 'running', 'trail_running',
            'treadmill_running', 'cycling', 'lap_swimming')
    

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": {
      "activity_id": "<activity_id>",
      "type_key": "<type_key>"
    },
    "name": "set_activity_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
type_keyYes
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the mutation risk is carried by structured fields. The description adds useful context about what specifically is mutated (only the sport classification) but does not say whether the previous type is recoverable, whether other activity data is preserved, or what happens on an invalid or unchanged type_key. Given the destructive flag, a note on reversibility would have been valuable.

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?

Purpose and example are front-loaded in the first two sentences, and the Args block is easy to scan. The docstring-style formatting is slightly verbose for a two-parameter tool, but every sentence carries information an agent would otherwise have to guess.

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 two-required-parameter mutation with no output schema, the description covers what it does, when it applies, where to find valid keys, and what each argument means. The remaining gap is post-call behavior — there is no indication of what a successful response contains or how errors (unknown type_key, unknown activity) surface.

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?

Schema description coverage is 0%, so the description must carry the burden — and it does, documenting both parameters in an Args block: activity_id as the ID of the activity to update, and type_key as the target type key with five concrete string examples. It does not enumerate the full valid set, but it correctly delegates that to get_activity_types and shows enough examples that an agent can format the value.

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?

States a specific verb and resource — 'Change the activity type (sport) of an activity' — and the parenthetical '(sport)' plus the trail_running→running example makes clear it edits the classification rather than, say, the event type handled by set_activity_event_type. It stops short of naming that sibling explicitly, so an agent still has to infer the boundary from the noun alone.

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?

Gives a concrete use case ('reclassifying a mislabelled activity') with two before/after examples, which tells the agent the right situation to reach for this tool. It also routes the agent to get_activity_types for the vocabulary of valid keys. There are no explicit when-not-to-use conditions or prerequisites (e.g. whether the activity must be downloaded or owned by the user).

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