Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-recovery-for-cycle

Retrieve recovery metrics for a specific WHOOP cycle using its ID to analyze physiological data and track fitness progress.

Instructions

Get recovery data for a specific cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycleIdYesID of the cycle to get recovery data for

Implementation Reference

  • Core handler function that performs the HTTP GET request to the Whoop API to retrieve recovery data for the specified cycle ID.
    async getRecoveryForCycle(cycleId: number): Promise<WhoopRecovery[]> {
      const response = await this.client.get(`/cycle/${cycleId}/recovery`);
      return response.data;
    }
  • Tool registration in MCP server including name, description, and input schema validation.
    {
      name: 'whoop-get-recovery-for-cycle',
      description: 'Get recovery data for a specific cycle',
      inputSchema: {
        type: 'object',
        properties: {
          cycleId: {
            type: 'number',
            description: 'ID of the cycle to get recovery data for',
          },
        },
        required: ['cycleId'],
      },
    },
  • MCP tool request handler that validates arguments, delegates to WhoopApiClient, and formats response as MCP content.
    case 'whoop-get-recovery-for-cycle': {
      if (!args || typeof args.cycleId !== 'number') {
        throw new Error('cycleId is required and must be a number');
      }
      const result = await this.whoopClient.getRecoveryForCycle(args.cycleId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
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 states the action ('Get') but does not mention whether this is a read-only operation, requires authentication, has rate limits, or describes the return format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 does not explain what 'recovery data' entails, the response format, or any behavioral traits like error handling. For a tool with no structured support, more detail is needed to be fully helpful.

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, with the 'cycleId' parameter clearly documented. The description adds no additional meaning beyond the schema, such as format details or examples. Baseline score of 3 is appropriate as the schema handles the heavy lifting.

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 ('recovery data for a specific cycle'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'whoop-get-recovery-collection' or 'whoop-get-cycle-by-id', which might also involve recovery or cycle data, so it falls short of 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-recovery-collection' for multiple cycles or 'whoop-get-cycle-by-id' for general cycle data. It lacks context on prerequisites or exclusions, leaving usage unclear.

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