Skip to main content
Glama
Sign In
Strava MCP Server

Strava MCP Server

by justmytwospence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Activity

strava_get_activity
Read-onlyIdempotent

Get detailed information about a specific activity including description, calories, splits, laps, segment efforts, best efforts, and gear. Served from the local mirror; recent activities are refreshed from Strava.

Instructions

Get detailed information about a specific activity including description, calories, splits, laps, segment efforts, best efforts, and gear. Served from the local mirror; recent activities are refreshed from Strava.

Input Schema

NameRequiredDescriptionDefault
activity_idYesThe activity ID
include_all_effortsNoIgnored: the mirror stores every segment effort and always returns them all. Kept for compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv4.4.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / activity_id / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / activity_id / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / include_all_efforts / default
      Removed value: -false
    • changedInput schema / properties / include_all_efforts / description
      Previous value: -"Include all segment efforts (can be very large). Default false."New value: +"Ignored: the mirror stores every segment effort and always returns them all. Kept for compatibility."
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, and the description adds genuinely new context: results come from a local mirror with recent activities refreshed from Strava, which tells the agent data may be stale and that a network refresh can occur. It stops short of describing staleness windows or refresh failure behavior.

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?

Two sentences, the resource and returned fields front-loaded, then the mirror/refresh caveat. Nothing is wasted or buried.

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 output schema, the description correctly enumerates what comes back, so an agent knows the response shape. It omits error behavior for unknown or non-mirrored activity IDs, which is a modest gap for a single-ID lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema carries the burden; activity_id is documented there and include_all_efforts is explicitly flagged as ignored for compatibility. The description adds only the indirect hint that segment efforts are always returned in bulk, so baseline 3 applies.

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 ('Get detailed information') plus resource ('a specific activity') and enumerates the payload fields (description, calories, splits, laps, segment efforts, best efforts, gear), which is enough to separate it from strava_list_activities and the narrower lap/zone/stream siblings.

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?

Implies usage via 'specific activity' but never states when to prefer this over strava_get_activity_streams, strava_list_activity_laps or strava_list_activity_zones, even though it claims to return laps and segment efforts that overlap those siblings. No exclusions or prerequisites are given.

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