Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-recovery-collection

Retrieve paginated recovery data from WHOOP to analyze user recovery metrics over time with date range filtering.

Instructions

Get all recovery data for a user, paginated

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit on the number of recovery records returned (max 25)
startNoReturn recovery records that occurred after or during this time (ISO 8601)
endNoReturn recovery records that intersect this time or ended before this time (ISO 8601)
nextTokenNoNext token from the previous response to get the next page

Implementation Reference

  • MCP server handler for the 'whoop-get-recovery-collection' tool: extracts pagination parameters from input arguments, calls WhoopApiClient.getRecoveryCollection, and returns the result as a JSON-formatted text response.
    case 'whoop-get-recovery-collection': {
      const result = await this.whoopClient.getRecoveryCollection({
        limit: args?.limit as number | undefined,
        start: args?.start as string | undefined,
        end: args?.end as string | undefined,
        nextToken: args?.nextToken as string | undefined,
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Tool registration in the ListTools response, including name, description, and input schema definition for pagination parameters.
      name: 'whoop-get-recovery-collection',
      description: 'Get all recovery data for a user, paginated',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Limit on the number of recovery records returned (max 25)',
          },
          start: {
            type: 'string',
            description: 'Return recovery records that occurred after or during this time (ISO 8601)',
          },
          end: {
            type: 'string',
            description: 'Return recovery records that intersect this time or ended before this time (ISO 8601)',
          },
          nextToken: {
            type: 'string',
            description: 'Next token from the previous response to get the next page',
          },
        },
        required: [],
      },
    },
  • Input schema definition for the tool, specifying optional pagination parameters: limit, start, end, nextToken.
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Limit on the number of recovery records returned (max 25)',
          },
          start: {
            type: 'string',
            description: 'Return recovery records that occurred after or during this time (ISO 8601)',
          },
          end: {
            type: 'string',
            description: 'Return recovery records that intersect this time or ended before this time (ISO 8601)',
          },
          nextToken: {
            type: 'string',
            description: 'Next token from the previous response to get the next page',
          },
        },
        required: [],
      },
    },
  • Core implementation logic: constructs URL query parameters from pagination inputs and performs GET request to Whoop API '/recovery' endpoint, returning the recovery collection data.
    async getRecoveryCollection(params?: PaginationParams): Promise<WhoopRecoveryCollection> {
      const queryParams = new URLSearchParams();
      
      if (params?.limit) queryParams.append('limit', params.limit.toString());
      if (params?.start) queryParams.append('start', params.start);
      if (params?.end) queryParams.append('end', params.end);
      if (params?.nextToken) queryParams.append('nextToken', params.nextToken);
    
      const url = `/recovery${queryParams.toString() ? `?${queryParams.toString()}` : ''}`;
      const response = await this.client.get(url);
      return response.data;
    }
Behavior3/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 pagination, which is a key behavioral trait not implied by the schema, but it does not cover other aspects like authentication needs, rate limits, or error handling. The description adds some value but is incomplete for a tool with no annotations.

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 front-loads the core purpose ('Get all recovery data for a user') and includes an important behavioral note ('paginated') without unnecessary words. It is appropriately sized and structured for clarity.

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 complexity (4 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose and pagination but lacks details on authentication, error cases, or output format, which are important for a data retrieval tool. It is adequate but has clear gaps in context.

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?

The input schema has 100% description coverage, so the schema fully documents the parameters. The description does not add any semantic details beyond what the schema provides, such as explaining interactions between parameters or default behaviors. This meets the baseline for high schema coverage.

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 ('Get') and resource ('all recovery data for a user'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'whoop-get-recovery-for-cycle', which might fetch recovery data for a specific cycle rather than all data, leaving some ambiguity in sibling distinction.

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 'whoop-get-recovery-for-cycle' for cycle-specific data or other collection tools. It lacks explicit context, prerequisites, or exclusions, offering minimal usage direction.

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