Skip to main content
Glama

export-route-tcx

Export Strava routes as TCX files for GPS devices or training software. Save routes to a local directory for offline use.

Instructions

Exports a specific Strava route in TCX format and saves it to a pre-configured local directory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
routeIdYesThe ID of the Strava route to export.

Implementation Reference

  • The implementation of the `execute` handler for the `export-route-tcx` tool.
    execute: async ({ routeId }: ExportRouteTcxInput) => {
        const token = process.env.STRAVA_ACCESS_TOKEN;
        if (!token) {
            // Strict return structure
            return {
                content: [{ type: "text" as const, text: "❌ Error: Missing STRAVA_ACCESS_TOKEN in .env file." }],
                isError: true
            };
        }
    
        const exportDir = process.env.ROUTE_EXPORT_PATH;
        if (!exportDir) {
            // Strict return structure
            return {
                content: [{ type: "text" as const, text: "❌ Error: Missing ROUTE_EXPORT_PATH in .env file. Please configure the directory for saving exports." }],
                isError: true
            };
        }
    
        try {
             // Ensure the directory exists, create if not
            if (!fs.existsSync(exportDir)) {
                console.error(`Export directory ${exportDir} not found, creating it...`);
                fs.mkdirSync(exportDir, { recursive: true });
            } else {
                // Check if it's a directory and writable (existing logic)
                const stats = fs.statSync(exportDir);
                if (!stats.isDirectory()) {
                    // Strict return structure
                    return {
                        content: [{ type: "text" as const, text: `❌ Error: ROUTE_EXPORT_PATH (${exportDir}) is not a valid directory.` }],
                        isError: true
                    };
                }
                fs.accessSync(exportDir, fs.constants.W_OK);
            }
    
            const tcxData = await fetchTcxData(token, routeId);
            const filename = `route-${routeId}.tcx`;
            const fullPath = path.join(exportDir, filename);
            fs.writeFileSync(fullPath, tcxData);
    
            // Strict return structure
            return {
                content: [{ type: "text" as const, text: `✅ Route ${routeId} exported successfully as TCX to: ${fullPath}` }],
            };
    
        } catch (err: any) {
            // Handle potential errors during directory creation/check or file writing
            console.error(`Error in export-route-tcx tool for route ${routeId}:`, err);
            let userMessage = `❌ Error exporting route ${routeId} as TCX: ${err.message}`;
             if (err.code === 'EACCES') {
                 userMessage = `❌ Error: No write permission for ROUTE_EXPORT_PATH directory (${exportDir}).`;
             }
            // Strict return structure
            return {
                content: [{ type: "text" as const, text: userMessage }],
                isError: true
            };
        }
    },
  • Input schema definition for the `export-route-tcx` tool.
    const ExportRouteTcxInputSchema = z.object({
        routeId: z.string().describe("The ID of the Strava route to export."),
    });
  • Registration of the `export-route-tcx` tool with its name, description, schema, and handler.
    export const exportRouteTcx = {
        name: "export-route-tcx",
        description: "Exports a specific Strava route in TCX format and saves it to a pre-configured local directory.",
        inputSchema: ExportRouteTcxInputSchema,
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a write operation (saves to local directory), requires a pre-configured destination, and outputs a file. However, it doesn't mention error conditions, file naming conventions, or what happens if the directory doesn't exist.

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 contains all essential information: action, resource, format, and destination. Every word earns its place with zero wasted text.

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

Completeness4/5

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

For a single-parameter tool with no output schema and no annotations, the description is reasonably complete. It explains what the tool does and where the output goes. However, it could benefit from mentioning error handling or file system implications.

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 already documents the single 'routeId' parameter. The description doesn't add any additional parameter semantics beyond what the schema provides, maintaining the baseline score.

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 clearly states the specific action ('Exports'), resource ('a specific Strava route'), format ('in TCX format'), and destination ('saves it to a pre-configured local directory'). It distinguishes from sibling 'export-route-gpx' by specifying TCX format.

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?

The description provides clear context for when to use this tool (exporting a route in TCX format to local storage). It doesn't explicitly mention when not to use it or name alternatives, but the TCX format specification naturally differentiates it from GPX export.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LimeON-source/Strava-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server