Skip to main content
Glama
Sign In
Strava Planner MCP

Strava Planner MCP

by Mohith1612
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Strava Activity Streams

getActivityStreams
Read-only

Retrieve detailed activity streams for point-by-point analysis, selecting only needed types to control response size.

Instructions

Use for point-by-point analysis. Request only needed stream types to control response size; omitted streamTypes selects a useful set based on activity metadata. Strava returns only available streams.

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

Input Schema

NameRequiredDescriptionDefault
activityIdYes
streamTypesNoRequested streams, e.g. time, distance, heartrate, velocity_smooth, cadence, altitude, grade_smooth, temp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Adds behavioral context beyond annotations: 'Strava returns only available streams' and describes default selection behavior when streamTypes is omitted. Annotations already indicate readOnlyHint=true.

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, front-loaded with purpose, no wasted words. Efficient and clear.

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

Completeness5/5

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

Given 2 parameters, no output schema, and annotations present, the description fully explains purpose, parameter usage, and behavioral notes. Complete for agent use.

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 50% schema coverage, description adds meaning: explains default behavior for omitted streamTypes and advises on controlling response size. ActivityId is implicitly understood.

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?

Clearly states 'Use for point-by-point analysis' and implies retrieval of activity streams. Distinguishes from siblings like getActivity which likely returns summary data.

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?

Advises to request only needed stream types to control response size and notes that omitting streamTypes selects a useful default set. Provides clear guidance on parameter usage.

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