Strava MCP Server

explore-segments

Search for popular running or cycling segments within a specified geographical area to discover challenging routes and climbs.

Instructions

Searches for popular segments within a given geographical area.

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": {
      "bounds": "<bounds>"
    },
    "name": "explore-segments"
  }
}

Input Schema

Name	Required	Description
`bounds`	Yes	The geographical area to search, specified as a comma-separated string: south_west_lat,south_west_lng,north_east_lat,north_east_lng
`activityType`	No	Filter segments by activity type (optional: 'running' or 'riding').
`minCat`	No	Filter by minimum climb category (optional, 0-5). Requires riding activityType.
`maxCat`	No	Filter by maximum climb category (optional, 0-5). Requires riding activityType.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions searching for 'popular segments' but doesn't specify what makes a segment 'popular' (e.g., based on usage, ratings, or other metrics), nor does it describe the return format, pagination, or any rate limits or authentication requirements. This leaves significant gaps in understanding the tool's 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?

The description is a single, clear sentence that efficiently conveys the core functionality without unnecessary words. It is front-loaded with the main action and resource, making it easy to understand at a glance.

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 complexity of a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., how popularity is determined, result format), usage context, and differentiation from siblings. This makes it inadequate for an AI agent to fully understand when and how to invoke the tool 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?

The schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond implying a geographical search, which is already covered by the 'bounds' parameter description. Thus, it meets the baseline score of 3 without adding extra value.

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 with a specific verb ('searches') and resource ('popular segments'), and specifies the geographical scope. However, it doesn't differentiate from sibling tools like 'list-starred-segments' or 'get-segment', which might also retrieve segments but with different criteria or scope.

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 like 'list-starred-segments' or 'get-segment', nor does it mention prerequisites such as requiring a connected Strava account. It only states what the tool does without contextual usage advice.

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