Skip to main content
Glama

disconnect-strava

Remove your Strava account connection and delete stored credentials to log out or disconnect from the Strava MCP Server.

Instructions

Disconnect your Strava account and remove stored credentials. Use this when the user wants to logout, disconnect, or remove their Strava connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `disconnect-strava` tool, which clears configuration and removes environment variables related to Strava.
    export const disconnectStravaTool = {
        name: 'disconnect-strava',
        description: 'Disconnect your Strava account and remove stored credentials. Use this when the user wants to logout, disconnect, or remove their Strava connection.',
        inputSchema: z.object({}),
        execute: async (): Promise<{ content: Array<{ type: 'text'; text: string }> }> => {
            try {
                const { clearConfig } = await import('../config.js');
                await clearConfig();
                
                // Clear from process.env as well
                delete process.env.STRAVA_ACCESS_TOKEN;
                delete process.env.STRAVA_REFRESH_TOKEN;
                
                return {
                    content: [{
                        type: 'text' as const,
                        text: '✅ Disconnected from Strava. Your credentials have been removed.\n\nTo reconnect, just say "Connect my Strava account".',
                    }],
                };
            } catch (error: any) {
                return {
                    content: [{
                        type: 'text' as const,
                        text: `❌ Error disconnecting: ${error.message}`,
                    }],
                };
            }
        },
    };
Behavior4/5

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

With no annotations provided, the description carries the full burden and effectively discloses key behavioral traits: it's a destructive operation ('remove stored credentials') and implies authentication needs ('your Strava account'). However, it doesn't mention potential side effects like data loss or rate limits.

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 front-loaded with the core purpose in the first sentence and adds usage context in the second, with no wasted words. Every sentence earns its place by providing essential information.

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 destructive tool with no annotations and no output schema, the description is reasonably complete—it explains the action and usage context. However, it could be more thorough by detailing potential consequences (e.g., data deletion) or confirmation steps, given the tool's complexity.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description adds no parameter information, which is appropriate given the lack of parameters, 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 ('Disconnect your Strava account and remove stored credentials') and distinguishes it from siblings like 'connect-strava' and 'check-strava-connection' by focusing on removal rather than connection or verification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool ('when the user wants to logout, disconnect, or remove their Strava connection'), providing clear context and distinguishing it from alternatives like 'connect-strava' for establishing connections.

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