Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-workout-collection

Retrieve paginated workout records for a user with optional time filters and result limits to analyze fitness activity history.

Instructions

Get all workout records for a user, paginated

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit on the number of workout records returned (max 25)
startNoReturn workout records that occurred after or during this time (ISO 8601)
endNoReturn workout 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

  • Core handler function that fetches paginated workout collection from Whoop API using axios GET request to /activity/workout with query parameters.
    async getWorkoutCollection(params?: PaginationParams): Promise<WhoopWorkoutCollection> {
      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/workout${queryParams.toString() ? `?${queryParams.toString()}` : ''}`;
      const response = await this.client.get(url);
      return response.data;
    }
  • MCP server tool handler case that invokes the WhoopApiClient.getWorkoutCollection method and formats the response as MCP content.
    case 'whoop-get-workout-collection': {
      const result = await this.whoopClient.getWorkoutCollection({
        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 and input schema definition returned by listTools, specifying the name, description, and input parameters for validation.
    {
      name: 'whoop-get-workout-collection',
      description: 'Get all workout records for a user, paginated',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Limit on the number of workout records returned (max 25)',
          },
          start: {
            type: 'string',
            description: 'Return workout records that occurred after or during this time (ISO 8601)',
          },
          end: {
            type: 'string',
            description: 'Return workout 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: [],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only mentions pagination behavior. It lacks critical details: authentication requirements, rate limits, error handling, response format, or whether it's read-only. 'Get' implies read-only, but this isn't explicitly stated, leaving gaps for a tool with 4 parameters.

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 key information: action, resource, and pagination. There's no wasted verbiage, and it directly addresses the core functionality without redundancy.

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?

For a tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It omits authentication needs, response structure, error cases, and usage context. While concise, it fails to provide the completeness needed for effective agent operation.

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 parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying date-range filtering via 'paginated' context. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 workout records for a user'), making the purpose understandable. It distinguishes from sibling tools like 'whoop-get-workout-by-id' by specifying collection vs. single record retrieval. However, it doesn't explicitly differentiate from other collection tools like 'whoop-get-cycle-collection' beyond the resource type.

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., authentication), compare to other collection tools, or specify use cases. The agent must infer usage from the name and parameters alone.

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