Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-revoke-user-access

Revoke user access tokens to terminate WHOOP API authorization and secure fitness data access.

Instructions

Revoke the access token granted by the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server tool handler for 'whoop-revoke-user-access' that calls the WhoopApiClient method and returns success response.
    case 'whoop-revoke-user-access': {
      await this.whoopClient.revokeUserAccess();
      return {
        content: [
          {
            type: 'text',
            text: 'User access revoked successfully',
          },
        ],
      };
    }
  • Core implementation in WhoopApiClient: sends DELETE request to Whoop API endpoint '/user/access' to revoke user access.
    async revokeUserAccess(): Promise<void> {
      await this.client.delete('/user/access');
    }
  • Tool registration in the ListTools response, including name, description, and input schema (no parameters required).
    {
      name: 'whoop-revoke-user-access',
      description: 'Revoke the access token granted by the user',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Input schema definition for the tool (empty object, no required parameters).
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
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 states the action ('revoke') but does not explain effects (e.g., whether this invalidates the token permanently, requires re-authorization, or impacts other sessions). No details on authentication needs, rate limits, or error handling are included, leaving significant gaps.

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, making it highly concise and front-loaded. Every word contributes directly to explaining the tool's purpose, earning a perfect score for efficiency.

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

Completeness2/5

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

Given the complexity of a token revocation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral outcomes (e.g., what happens after revocation), error cases, or integration with sibling tools, making it insufficient for safe and effective use by an AI 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 does not add parameter details, which is appropriate, but it could have mentioned implicit context (e.g., token revocation based on current session). Baseline is 4 due to zero parameters.

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 action ('revoke') and the resource ('access token granted by the user'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'whoop-refresh-token' or 'whoop-set-access-token', 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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'whoop-refresh-token' for renewing access or 'whoop-set-access-token' for setting a new token). The description implies usage for revoking tokens but lacks context on prerequisites or scenarios, such as after user logout or security concerns.

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/nissand/whoop-mcp-server-claude'

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