Strava MCP Server

get_activity_streams

Retrieve detailed time-series data for Strava activities, including GPS coordinates, heart rate, power, cadence, altitude, and velocity metrics to analyze performance.

Instructions

Get detailed time-series data (streams) for an activity: GPS coordinates, heartrate, power, cadence, altitude, etc.

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

Input Schema

Name	Required	Description	Default
`activity_id`	Yes	The Strava activity ID
`stream_types`	No	Types of streams to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 22, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving data but does not cover aspects like rate limits, authentication requirements, error conditions, or the format of the returned streams. This leaves significant gaps for an agent to understand how to use the tool effectively.

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 description is a single, efficient sentence that front-loads the core purpose and provides relevant examples without unnecessary details. Every word earns its place, making it easy to parse and understand quickly.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the returned data looks like (e.g., format, structure), potential limitations, or error handling. For a tool that retrieves detailed time-series data, more context is needed to guide an agent effectively.

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 description coverage is 100%, so the schema fully documents the parameters. The description adds minimal value by implying that 'stream_types' includes examples like GPS coordinates and heartrate, but does not provide additional semantics beyond what the schema already specifies (e.g., default values or enum details). Baseline score of 3 is appropriate.

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 clearly states the tool's purpose: retrieving detailed time-series data (streams) for an activity, with specific examples like GPS coordinates, heartrate, power, cadence, and altitude. It uses a specific verb ('Get') and resource ('activity'), but does not explicitly differentiate from sibling tools like 'get_activity' or 'get_activities', which might retrieve different types of activity data.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'get_activity' (which might retrieve summary data) or specify contexts where detailed streams are needed over other data types. Usage is implied by the description but not explicitly stated.

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

Deploy Server