Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-cycle-by-id

Retrieve detailed fitness and health cycle data from WHOOP by specifying a cycle ID to access recovery metrics, sleep analysis, and workout information.

Instructions

Get the cycle for the specified ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycleIdYesID of the cycle to retrieve

Implementation Reference

  • Registration of the MCP tool 'whoop-get-cycle-by-id' including its description and input schema definition.
      name: 'whoop-get-cycle-by-id',
      description: 'Get the cycle for the specified ID',
      inputSchema: {
        type: 'object',
        properties: {
          cycleId: {
            type: 'number',
            description: 'ID of the cycle to retrieve',
          },
        },
        required: ['cycleId'],
      },
    },
  • MCP CallToolRequest handler case for 'whoop-get-cycle-by-id' that performs input validation and calls the WhoopApiClient to execute the tool logic.
    case 'whoop-get-cycle-by-id': {
      if (!args || typeof args.cycleId !== 'number') {
        throw new Error('cycleId is required and must be a number');
      }
      const result = await this.whoopClient.getCycleById(args.cycleId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Core helper function in WhoopApiClient that makes the HTTP GET request to the Whoop API endpoint `/cycle/{cycleId}` to fetch the cycle data.
    async getCycleById(cycleId: number): Promise<WhoopCycle> {
      const response = await this.client.get(`/cycle/${cycleId}`);
      return response.data;
    }
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 retrieval but doesn't specify if it's a read-only operation, requires authentication, has rate limits, or what the response format might be. This leaves significant gaps for a tool that likely interacts with an API.

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 directly states the tool's function without any unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain behavioral aspects like authentication needs or response format, which are crucial for a tool that likely fetches data from an external service. More context is needed for effective use.

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 schema description coverage is 100%, with the parameter 'cycleId' fully documented in the schema. The description adds no additional meaning beyond what's in the schema, such as format details or examples, so it 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 ('cycle for the specified ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'whoop-get-cycle-collection' or 'whoop-get-recovery-for-cycle', which also involve cycles, so it lacks sibling distinction for a perfect score.

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-cycle-collection' for multiple cycles or 'whoop-get-recovery-for-cycle' for related data. It only states what it does, without context or exclusions.

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