Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-cycle-collection

Retrieve paginated physiological cycle data from WHOOP to analyze fitness patterns, track recovery metrics, and monitor sleep cycles over time.

Instructions

Get all physiological cycles for a user, paginated

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit on the number of cycles returned (max 25)
startNoReturn cycles that occurred after or during this time (ISO 8601)
endNoReturn cycles 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 tool handler switch case that delegates the tool execution to WhoopApiClient.getCycleCollection and returns the result as JSON-formatted text content.
    case 'whoop-get-cycle-collection': {
      const result = await this.whoopClient.getCycleCollection({
        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 handler, defining the tool name, description, and input schema.
    {
      name: 'whoop-get-cycle-collection',
      description: 'Get all physiological cycles for a user, paginated',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Limit on the number of cycles returned (max 25)',
          },
          start: {
            type: 'string',
            description: 'Return cycles that occurred after or during this time (ISO 8601)',
          },
          end: {
            type: 'string',
            description: 'Return cycles 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 helper function in WhoopApiClient that constructs pagination query parameters and fetches cycle collection data from the Whoop API.
    async getCycleCollection(params?: PaginationParams): Promise<WhoopCycleCollection> {
      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 = `/cycle${queryParams.toString() ? `?${queryParams.toString()}` : ''}`;
      const response = await this.client.get(url);
      return response.data;
    }
  • TypeScript interface defining the input parameters for getCycleCollection, matching the tool's inputSchema.
    export interface PaginationParams {
      limit?: number;
      start?: string;
      end?: string;
      nextToken?: string;
    }
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 mentions pagination, which is useful, but fails to describe authentication requirements, rate limits, error handling, or the structure of returned data (e.g., what fields are included in cycles). For a tool with no annotations, this leaves significant gaps in understanding its operation.

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 physiological cycles for a user') and adds a key behavioral trait ('paginated') without unnecessary words. Every part of the sentence provides value, 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 no annotations and no output schema, the description is incomplete for a tool with four parameters and pagination. It adequately states the purpose but lacks details on authentication, response format, error cases, or usage context relative to siblings. This is minimally viable but has clear gaps in providing a full operational picture.

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 (limit, start, end, nextToken). The description adds no parameter-specific information beyond implying date-range filtering via 'paginated', which is already covered by the schema. This meets the baseline of 3 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 all physiological cycles') and resource ('for a user'), with the additional detail 'paginated' indicating the response format. It distinguishes from sibling tools like 'whoop-get-cycle-by-id' by specifying collection vs. single item retrieval, though it doesn't explicitly contrast with all siblings like 'whoop-get-recovery-collection'.

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

Usage Guidelines3/5

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

The description implies usage for retrieving multiple cycles rather than a single one, which differentiates it from 'whoop-get-cycle-by-id'. However, it lacks explicit guidance on when to use this tool versus other collection tools (e.g., 'whoop-get-sleep-collection'), prerequisites (e.g., authentication), or exclusions (e.g., no filtering by user ID).

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