Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-workout-by-id

Retrieve detailed workout data from WHOOP by providing a specific workout ID to access performance metrics and exercise records.

Instructions

Get the workout record for the specified ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workoutIdYesID of the workout record to retrieve

Implementation Reference

  • MCP server tool handler: validates workoutId input and calls WhoopApiClient.getWorkoutById to fetch and return the workout data as JSON.
    case 'whoop-get-workout-by-id': {
      if (!args || typeof args.workoutId !== 'string') {
        throw new Error('workoutId is required and must be a string');
      }
      const result = await this.whoopClient.getWorkoutById(args.workoutId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Core API client method that performs the HTTP GET request to Whoop's /activity/workout/{workoutId} endpoint and returns the workout object.
    async getWorkoutById(workoutId: string): Promise<WhoopWorkout> {
      const response = await this.client.get(`/activity/workout/${workoutId}`);
      return response.data;
    }
  • Tool registration in the listTools response, defining name, description, and input schema (workoutId: string).
      name: 'whoop-get-workout-by-id',
      description: 'Get the workout record for the specified ID',
      inputSchema: {
        type: 'object',
        properties: {
          workoutId: {
            type: 'string',
            description: 'ID of the workout record to retrieve',
          },
        },
        required: ['workoutId'],
      },
    },
  • TypeScript interface defining the output structure of the Whoop workout data.
    export interface WhoopWorkout {
      id: string;
      v1_id: number;
      user_id: number;
      created_at: string;
      updated_at: string;
      start: string;
      end: string;
      timezone_offset: string;
      sport_name: string;
      sport_id: number;
      score_state: string;
      score?: WhoopWorkoutScore;
    }
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 states the tool retrieves a workout record but lacks details on permissions, rate limits, error handling, or response format. This is a significant gap for a tool with potential API constraints.

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 purpose without unnecessary words. It is appropriately sized and front-loaded, with every element contributing to clarity.

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 address behavioral aspects like authentication needs or response structure, leaving gaps for a tool that likely interacts with an external API and returns data.

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 'workoutId' fully documented in the schema. The description adds no additional meaning beyond implying retrieval by ID, so it meets the baseline of 3 without compensating for any gaps.

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 ('workout record'), specifying retrieval by ID. It distinguishes from sibling tools like 'whoop-get-workout-collection' by focusing on a single record rather than a collection, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives such as 'whoop-get-workout-collection' for multiple workouts or other ID-based tools like 'whoop-get-cycle-by-id'. The description implies usage for retrieving a specific workout but offers no explicit 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