Skip to main content
Glama

set_perceived_effort

Destructive

Update an activity's perceived effort (RPE) using Garmin Connect's 0–10 rating; set 0 to clear it and the tool converts the stored value automatically.

Instructions

Set the perceived effort (RPE) for an activity.

    Mirrors Garmin Connect's 'Perceived Effort' rating on a 0-10 scale,
    where 0 clears the rating. Internally Garmin stores this multiplied by
    10 (so RPE 7 is stored as 70); this tool handles the conversion.

    Args:
        activity_id: ID of the activity to update
        rpe: Perceived effort from 0 to 10 (0 clears the rating)
    

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>",
      "rpe": "<rpe>"
    },
    "name": "set_perceived_effort"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpeYes
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, destructive, non-idempotent, open-world write, so the safety profile is partly covered. The description adds genuinely useful behavior beyond that: the 0 clears the rating semantics (which explains the destructive hint) and the internal ×10 storage conversion the tool handles. It does not state that an existing rating is overwritten or what happens for out-of-range values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and the scale semantics are front-loaded in the first sentence, followed by only the details that change behavior (0 clears, ×10 conversion) and a compact Args block. No filler sentences.

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 setter with no output schema and full annotation coverage, the description supplies everything needed to invoke it correctly: target resource, value range, and the clearing value. Missing only error/overwrite behavior and confirmation of what the call returns.

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 carries the full burden and does so: activity_id is described as the ID of the activity to update, and rpe is bounded to a 0-10 scale with 0 meaning clear. The only gap is that the anyOf integer-or-string acceptance of activity_id is left to the schema.

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 opens with a specific verb and resource ("Set the perceived effort (RPE) for an activity"), which is distinguishable from siblings like set_activity_feel or set_activity_description by naming the exact field. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than 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 Guidelines3/5

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

Usage is implied by the narrow single-field scope and by the explanation that RPE 0 clears the rating, which tells the agent how to use a special value. There is no explicit statement of when to prefer this over set_activity_feel or another sibling, and no stated prerequisites (e.g., activity must already exist).

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