Skip to main content
Glama

get-athlete-shoes

Retrieve your Strava running shoes data including usage distance and primary shoe status to track gear wear and optimize training equipment.

Instructions

Fetches the authenticated athlete's shoes from Strava, including usage distance and primary flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the get-athlete-shoes tool handler.
    export const getAthleteShoesTool = {
        name: "get-athlete-shoes",
        description: "Fetches the authenticated athlete's shoes from Strava, including usage distance and primary flag.",
        inputSchema: undefined,
        execute: async () => {
            const token = process.env.STRAVA_ACCESS_TOKEN;
    
            if (!token || token === 'YOUR_STRAVA_ACCESS_TOKEN_HERE') {
                console.error("Missing or placeholder STRAVA_ACCESS_TOKEN in .env");
                return {
                    content: [{ type: "text" as const, text: "❌ Configuration Error: STRAVA_ACCESS_TOKEN is missing or not set in the .env file." }],
                    isError: true,
                };
            }
    
            try {
                console.error("Fetching athlete shoes...");
                const athlete = await getAuthenticatedAthlete(token);
                const shoes = athlete.shoes ?? [];
    
                if (shoes.length === 0) {
                    return {
                        content: [{ type: "text" as const, text: "No shoes found in your Strava profile." }],
                    };
                }
    
                const lines = shoes.map((shoe, index) => {
                    const distanceKm = typeof shoe.distance === "number" ? (shoe.distance / 1000).toFixed(2) : "N/A";
                    return `${index + 1}. ${shoe.name} (ID: ${shoe.id})\n   - Distance: ${distanceKm} km\n   - Primary: ${shoe.primary ? "Yes" : "No"}`;
                });
    
                return {
                    content: [{
                        type: "text" as const,
                        text: `👟 **Your Strava Shoes** (Total: ${shoes.length})\n\n${lines.join("\n\n")}`,
                    }],
                };
            } catch (error) {
                const errorMessage = error instanceof Error ? error.message : "An unknown error occurred";
                console.error("Error in get-athlete-shoes tool:", errorMessage);
                return {
                    content: [{ type: "text" as const, text: `❌ API Error: ${errorMessage}` }],
                    isError: true,
                };
            }
        }
    };
  • src/server.ts:173-179 (registration)
    Registration of the get-athlete-shoes tool in the main MCP server file.
    // --- Register get-athlete-shoes tool ---
    server.tool(
        getAthleteShoesTool.name,
        getAthleteShoesTool.description,
        {},
        getAthleteShoesTool.execute
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, if it requires specific permissions, rate limits, or how data is returned (e.g., pagination, format). The mention of 'authenticated athlete' hints at auth needs but is vague.

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, well-structured sentence that front-loads the core action and includes key details (resource, source, data included) without any wasted words, making it highly efficient and easy to parse.

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?

For a tool with 0 parameters and no output schema, the description is adequate but incomplete. It specifies what data is fetched but not the return format or behavioral traits. Given the lack of annotations, more context on auth requirements or data structure would improve completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, maintaining focus on tool purpose without redundancy, earning a baseline score above 3 for efficiency.

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 ('fetches'), resource ('authenticated athlete's shoes from Strava'), and scope ('including usage distance and primary flag'), distinguishing it from sibling tools like get-athlete-profile or get-athlete-stats that focus on different athlete data.

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, such as whether it's for viewing shoe inventory versus activity-specific gear, or prerequisites like needing Strava authentication. It mentions 'authenticated athlete' but doesn't clarify if this requires prior connection steps.

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