Skip to main content
Glama

set_activity_feel

Destructive

Update an activity's feel rating on Garmin Connect using the 5-point scale (0–100) to capture how the activity felt.

Instructions

Set how an activity felt ('How did you feel?').

    Mirrors Garmin Connect's 5-point feel rating, stored as one of:
      0   = very tired / poor
      25  = tired
      50  = normal
      75  = good
      100 = strong
    Higher is better.

    Args:
        activity_id: ID of the activity to update
        feel: One of 0, 25, 50, 75, 100
    

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>",
      "feel": "<feel>"
    },
    "name": "set_activity_feel"
  }
}

Input Schema

NameRequiredDescriptionDefault
feelYes
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 safety profile is covered structurally. The description adds genuinely useful behavior semantics by enumerating the accepted rating scale and its meaning, but it never says that an existing feel value is overwritten, nor what happens with an invalid value or a nonexistent activity_id.

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 the purpose, followed by the value mapping that genuinely earns its space given the empty schema. The trailing Args block largely restates the schema field names, and 'Higher is better' is mildly redundant after the labeled scale.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, the value semantics are well covered, but a destructive overwrite tool should say what is replaced and what a successful call yields. The annotations supply the risk profile, so this is adequate rather than complete.

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% and the feel parameter has no enum, so the description carries the full burden — and it does, spelling out all five legal values (0/25/50/75/100) with their meanings and the direction of the scale. activity_id is only glossed as 'ID of the activity to update', leaving its accepted int-or-string form and lookup behavior unexplained.

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 description names a specific verb and resource ('Set how an activity felt') and explains the domain concept by tying it to Garmin Connect's 5-point feel rating. It does not, however, distinguish this from the closely related sibling set_perceived_effort, which an agent could easily confuse with a 'how did it feel' rating.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of when not to use it or which sibling to pick instead. The closest thing to context is the parenthetical 'How did you feel?', which implies the Garmin post-activity survey but never states it as a condition.

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