Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-sleep-collection

Retrieve paginated sleep records from WHOOP data, allowing filtering by date range and limiting results for comprehensive sleep analysis.

Instructions

Get all sleep records for a user, paginated

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit on the number of sleep records returned (max 25)
startNoReturn sleep records that occurred after or during this time (ISO 8601)
endNoReturn sleep 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-sleep-collection' tool. Parses arguments, calls WhoopApiClient.getSleepCollection, and returns the result as a JSON-formatted text response.
    case 'whoop-get-sleep-collection': {
      const result = await this.whoopClient.getSleepCollection({
        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 MCP server's ListTools handler, defining the name, description, and input schema for pagination parameters.
    {
      name: 'whoop-get-sleep-collection',
      description: 'Get all sleep records for a user, paginated',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Limit on the number of sleep records returned (max 25)',
          },
          start: {
            type: 'string',
            description: 'Return sleep records that occurred after or during this time (ISO 8601)',
          },
          end: {
            type: 'string',
            description: 'Return sleep 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: [],
      },
    },
  • Implementation of the sleep collection fetcher in WhoopApiClient. Builds query parameters from input and makes authenticated GET request to Whoop API's /activity/sleep endpoint.
    async getSleepCollection(params?: PaginationParams): Promise<WhoopSleepCollection> {
      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 = `/activity/sleep${queryParams.toString() ? `?${queryParams.toString()}` : ''}`;
      const response = await this.client.get(url);
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions pagination, which is useful, but lacks details on authentication requirements, rate limits, error handling, or the structure of returned data. For a read operation with zero annotation coverage, this leaves significant 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, efficient sentence that front-loads the core purpose ('Get all sleep records for a user') and includes a key behavioral trait ('paginated'). There is no wasted verbiage, making it appropriately sized and well-structured.

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 moderate complexity (4 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and pagination but lacks details on authentication, data format, or error handling. Without annotations or output schema, more context would be helpful for the agent to use it effectively.

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%, so the input schema fully documents all four parameters. The description adds no additional semantic information beyond what's in the schema, such as examples or edge cases. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 ('Get') and resource ('all sleep records for a user'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'whoop-get-sleep-by-id' or 'whoop-get-sleep-for-cycle', which target specific records rather than collections.

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 mentions pagination but doesn't specify scenarios where this collection tool is preferred over sibling tools like 'whoop-get-sleep-by-id' or 'whoop-get-sleep-for-cycle', leaving the agent without usage context.

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