Skip to main content
Glama

set_activity_description

Destructive

Set or update the notes field on a Garmin activity to record session feel, kit, conditions, or niggles; pass an empty string to clear it.

Instructions

Set or update the free-text description (notes) of an activity.

    This is the notes field shown on the activity page — useful for
    recording how a session felt, kit used, conditions, niggles, etc.
    Pass an empty string to clear an existing description.

    Args:
        activity_id: ID of the activity to update
        description: New description text (empty string clears it).
            Max 2000 characters; Garmin rejects longer.
            Emoji and other non-BMP characters count as two.
    

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>",
      "description": "<description>"
    },
    "name": "set_activity_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write nature is covered; the description adds genuinely new behavior: the 2000-character cap, Garmin rejecting longer input, emoji/non-BMP characters counting as two, and empty-string semantics for clearing. It stops short of explicitly saying the existing value is overwritten in place or what the response looks like, which keeps it below a 5.

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 a clarifying sentence about which field it is, then clearing rule, then parameter notes. The Args block is docstring-shaped rather than prose but every line carries substantive constraint information; nothing is redundant.

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-parameter mutation with no output schema and annotations that already flag destructiveness, the description supplies the limits and overwrite/clear semantics an agent needs to call it safely. Only the return value and the string-vs-integer ID form remain unstated.

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 carries the burden and does so for both parameters: activity_id is 'ID of the activity to update' and description covers content semantics, clearing behavior, and the length limit. The schema's anyOf (integer or string) for activity_id is not addressed, a minor remaining gap.

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 ('Set or update') and resource ('free-text description (notes) of an activity'), and further pins down the field as 'the notes field shown on the activity page', which implicitly separates it from the sibling set_activity_name. An agent can immediately tell which activity field this mutates.

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 concrete positive use cases ('recording how a session felt, kit used, conditions, niggles') and a clear clearing procedure ('Pass an empty string to clear an existing description'). It does not name when-not to use it or point at sibling setters such as set_activity_name, so the routing guidance is clear but incomplete.

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