Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-set-access-token

Configure API authentication by setting the access token required to retrieve WHOOP fitness and health data through the MCP server.

Instructions

Set the access token for API calls

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessTokenYesAccess token to use for API calls

Implementation Reference

  • Handler for the 'whoop-set-access-token' tool: validates the accessToken input and delegates to WhoopApiClient.setAccessToken, returning success message.
    case 'whoop-set-access-token': {
      if (!args || typeof args.accessToken !== 'string') {
        throw new Error('accessToken is required and must be a string');
      }
      this.whoopClient.setAccessToken(args.accessToken);
      return {
        content: [
          {
            type: 'text',
            text: 'Access token set successfully',
          },
        ],
      };
    }
  • Registration of the 'whoop-set-access-token' tool in the listTools handler, including name, description, and input schema.
    {
      name: 'whoop-set-access-token',
      description: 'Set the access token for API calls',
      inputSchema: {
        type: 'object',
        properties: {
          accessToken: {
            type: 'string',
            description: 'Access token to use for API calls',
          },
        },
        required: ['accessToken'],
      },
    },
  • Input schema definition for the 'whoop-set-access-token' tool.
    inputSchema: {
      type: 'object',
      properties: {
        accessToken: {
          type: 'string',
          description: 'Access token to use for API calls',
        },
      },
      required: ['accessToken'],
    },
  • Core helper method in WhoopApiClient that sets the access token in the config, which is used by the axios interceptor for Authorization headers in subsequent API calls.
    setAccessToken(accessToken: string) {
      this.config.accessToken = accessToken;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Set' implies a mutation, but the description doesn't specify whether this persists across sessions, affects all subsequent API calls, requires specific permissions, or has side effects. For a security-sensitive tool with zero annotation coverage, this minimal description leaves critical behavior undocumented.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information. Every word earns its place.

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 this is a security/mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'Set' actually means operationally (e.g., session persistence, scope), what happens on success/failure, or how this interacts with other authentication tools. For a tool that manages API credentials, this minimal description leaves too much undefined.

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%, with the single parameter 'accessToken' clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('Set') and the resource ('access token for API calls'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'whoop-exchange-code-for-token' or 'whoop-refresh-token' by focusing on manual token setting rather than token acquisition or refresh operations. However, it doesn't specify what API calls it affects or the scope of the setting.

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. It doesn't mention prerequisites (e.g., needing a token from another source), when this should be used instead of automated token exchange/refresh tools, or what happens if the token is invalid. With multiple authentication-related siblings, this lack of differentiation is a significant gap.

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