Skip to main content
Glama
Sign In
Strava MCP Server

Strava MCP Server

by justmytwospence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Export Route as TCX

strava_export_route_tcx
Read-onlyIdempotent

Export a route as a TCX file. Returns raw TCX XML content.

Instructions

Export a route as a TCX file. Returns raw TCX XML content.

Input Schema

NameRequiredDescriptionDefault
route_idYesThe route ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / route_id / pattern
      Added value: +"^[1-9]\\d{0,18}$"
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful output context by stating that the tool returns raw TCX XML content, which matters because there is no output schema.

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 two short, front-loaded sentences with no wasted text. It states the action first and the return format second.

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?

For a simple read-only export tool with complete schema coverage and full behavioral annotations, the description supplies the key missing piece: the raw TCX XML return format. Nothing essential for correct invocation is absent.

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% and the single route_id parameter is already documented in the schema. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 states a specific verb and resource ("Export a route") plus the output format ("TCX file"), clearly distinguishing it from strava_export_route_gpx and metadata-oriented siblings like strava_get_route.

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?

Usage is implied by the tool name and TCX format, but the description does not explicitly say when to choose this over strava_export_route_gpx or strava_get_route. No exclusions or alternatives are stated.

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