Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_activity_feel

Set or clear the feel rating for a Garmin Connect activity using 0, 25, 50, 75, or 100; pass null to remove it.

Instructions

"How did you feel?": 0, 25, 50, 75 or 100, or null to clear it. Partial PUT of summaryDTO.directWorkoutFeel, one of 0/25/50/75/100 ("How did you feel?", very weak to very strong); null clears it. Garmin stores any number (30 read back as 30) that its apps cannot display, so the method refuses anything else.

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

Input Schema

NameRequiredDescriptionDefault
feelYes
activityIdYesNumeric id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds real behavioral context beyond them: it is a *partial* PUT, `null` clears the field, and the method actively refuses values outside the allowed set rather than silently passing them. It does not mention auth requirements or failure modes when the activity is missing.

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

Conciseness3/5

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

The opening quote and the middle clause restate the same fact (the 0/25/50/75/100 domain is given twice, and `null` clearing is stated twice). The information is front-loaded, but roughly a third of the text is duplication.

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, the description covers the value domain, the clearing path, and validation behavior. It leaves the schema/description mismatch on `null` and any result/response expectations unaddressed.

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 coverage is 50% and the `feel` enum carries no description, so the description compensates by naming the five admissible values, their meaning scale (very weak to very strong), and the clearing semantics. Note the description's `null`-clears behavior is at odds with the schema, which requires `feel` and offers no null branch — helpful for the agent to know, but 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?

States a specific verb and target field: a partial PUT of `summaryDTO.directWorkoutFeel` on an activity, with the value domain spelled out. An agent can distinguish it from siblings like set_activity_perceived_effort or set_activity_description by the named field, though the description never explicitly says so.

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 when-to-use guidance, no mention of prerequisites (e.g. the activity must already exist / be a workout), and no routing away from the close sibling set_activity_perceived_effort. Usage is only implied by the parameter set.

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