Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand

whoop-get-user-body-measurements

Retrieve user body measurements including height, weight, and maximum heart rate from WHOOP fitness data to track physical metrics and health parameters.

Instructions

Get body measurements (height, weight, max heart rate) for the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration including name, description, and input schema (empty object).
      name: 'whoop-get-user-body-measurements',
      description: 'Get body measurements (height, weight, max heart rate) for the authenticated user',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • MCP server handler for the tool: calls WhoopApiClient.getUserBodyMeasurements() and returns the result as formatted JSON text.
    case 'whoop-get-user-body-measurements': {
      const result = await this.whoopClient.getUserBodyMeasurements();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Core implementation: Makes a GET request to Whoop API endpoint '/user/measurement/body' and returns the body measurements data.
    async getUserBodyMeasurements(): Promise<WhoopBodyMeasurements> {
      const response = await this.client.get('/user/measurement/body');
      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 implies a read-only operation ('Get') but doesn't specify authentication requirements, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this is insufficient, as critical behavioral traits are missing.

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 redundancy. It front-loads the key action and resource, making it easy to parse. Every word contributes to understanding, with no wasted text.

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 what the return values look like (e.g., data structure, units), authentication needs, or potential errors. For a data retrieval tool in a health/fitness context, more detail on output and behavior is warranted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. This meets the baseline for tools with no parameters, as it doesn't add unnecessary information.

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 ('body measurements for the authenticated user'), specifying the data types (height, weight, max heart rate). It distinguishes from siblings like 'whoop-get-user-profile' by focusing on body measurements rather than general profile data. However, it doesn't explicitly contrast with all siblings, keeping it at 4 rather than 5.

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 status), compare to similar tools like 'whoop-get-user-profile', or specify use cases. This lack of contextual direction leaves the agent without clear usage instructions.

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