Skip to main content
Glama
Sign In
Strava MCP Server

Strava MCP Server

by ArjanLig
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_recent_activities

Retrieve recent Strava activities to support training analysis and personalized coaching. Adjust retrieval limit up to 30 activities.

Instructions

Get recent Strava activities (default: last 10)

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": "get_recent_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of activities (max 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

B3.3/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 full burden. It does not disclose that the tool is read-only, lacks rate limit or authentication hints, and does not specify what happens if the limit exceeds 30. The minimal description fails to convey behavioral traits.

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 sentence with no unnecessary words. It efficiently conveys the essential information. Every word earns its place, making it extremely concise.

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

Completeness3/5

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

Given the tool is simple (1 parameter, no output schema, no nested objects), the description is minimally sufficient. However, it lacks details about the output structure (e.g., order, fields) and does not clarify if the tool requires authentication, which would help the agent. Slightly incomplete for a tool with no annotations.

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% for the single parameter 'limit'. The description's mention of 'default: last 10' merely echoes the schema default. It adds no additional semantic meaning beyond what the schema provides, meeting the baseline for high coverage.

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?

The description is specific: 'Get recent Strava activities' clearly states the verb and resource, and includes a default value. It distinguishes from sibling tools like get_activity_details and analysis tools, as it is the only tool for listing recent activities.

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?

No guidance on when to use this tool versus alternatives. There is no mention of context or exclusions. The description simply states what it does without advising when it is appropriate.

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