Skip to main content
Glama

list-athlete-clubs

Retrieve the Strava clubs you're currently a member of to manage your athletic community affiliations and track group activities.

Instructions

Lists the clubs the authenticated athlete is a member of.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `listAthleteClubs` object contains the tool definition, including its name, description, and the `execute` function which handles the logic of calling the Strava API and formatting the output.
    export const listAthleteClubs = {
        name: "list-athlete-clubs",
        description: "Lists the clubs the authenticated athlete is a member of.",
        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 clubs...");
                const clubs = await fetchClubs(token);
                console.error(`Successfully fetched ${clubs?.length ?? 0} clubs.`);
    
                if (!clubs || clubs.length === 0) {
                    return { content: [{ type: "text" as const, text: " MNo clubs found for the athlete." }] };
                }
    
                const clubText = clubs.map(club =>
                    `
    👥 **${club.name}** (ID: ${club.id})
       - Sport: ${club.sport_type}
       - Members: ${club.member_count}
       - Location: ${club.city}, ${club.state}, ${club.country}
       - Private: ${club.private ? 'Yes' : 'No'}
       - URL: ${club.url || 'N/A'}
            `.trim()
                ).join("\n---\n");
    
                const responseText = `**Your Strava Clubs:**\n\n${clubText}`;
    
                return { content: [{ type: "text" as const, text: responseText }] };
            } catch (error) {
                const errorMessage = error instanceof Error ? error.message : "An unknown error occurred";
                console.error("Error in list-athlete-clubs tool:", errorMessage);
                return {
                    content: [{ type: "text" as const, text: `❌ API Error: ${errorMessage}` }],
                    isError: true,
                };
            }
        }
    };
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 'authenticated athlete', implying an authentication requirement, but does not specify permissions, rate limits, or response format. This leaves 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 with no wasted words. It is front-loaded with the core action and resource, making it 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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose but lacks details on authentication, output format, or usage context, which could be helpful for an agent.

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, aligning with the schema. A baseline of 4 is applied since it avoids redundancy.

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 verb ('Lists') and resource ('clubs the authenticated athlete is a member of'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'list-athlete-routes' or 'list-starred-segments', which prevents a perfect score.

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 other list tools or related athlete data tools. It lacks context about prerequisites or typical scenarios for retrieving club memberships.

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