Skip to main content
Glama
Sign In

Strava MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update activity gear in Strava

strava_update_activity_gear
Read-onlyIdempotent

Update activity gear in the user's own Strava account from ChatGPT, Claude or any AI agent. Returns how to do it in Strava step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Strava Cloud Browser. Strava's official API: Strava has an official API and, since 1 June 2026, an official MCP connector (checked 27 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "strava_update_activity_gear"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false; the description reinforces that by stating it "opens nothing by itself," which resolves the obvious confusion with the mutating-sounding name. It also discloses what the return content looks like (steps, screens, buttons, fields), which annotations cannot convey. It omits any failure modes (e.g. if the Strava session is not authenticated).

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 core is front-loaded and efficient, but the trailing sentence about Strava's official API and MCP connector is tangential to invoking this tool and dilutes focus. Two of the four clauses could be trimmed without losing call-relevant information.

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?

With no input schema to speak of and no output schema, the description carries the burden of explaining what comes back, and it does so adequately by listing the step-by-step content. A note about prerequisites (active browser session, logged-in Strava account) would close the remaining gap.

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?

Zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly implies a no-argument call by describing the tool as a guide producer rather than a parameterized updater.

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?

Names a specific verb and resource ("Update activity gear in the user's own Strava account") and then clarifies the real behavior: it returns a step-by-step guide rather than performing the update. It distinguishes itself from the cotlet_browser_* siblings by naming them as the actual execution path. The name/behavior tension (an "update" tool that does not update) keeps it just short of 5.

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?

Clearly frames the workflow: call this to get screens/buttons/fields, then perform the change with cotlet_browser_* in the user's Cloud Browser. It does not state when NOT to use it (e.g. when the user has API access or wants no browser session), so it falls short of explicit alternatives/exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Strava MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources