Skip to main content
Glama
Sign In
whoop-mcp

whoop-mcp

by d00ennis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

whoop_workouts

Get workouts with strain, heart rate zones, distance, and calories. Optionally filter by sport, such as running.

Instructions

Trainingseinheiten mit Strain, Herzfrequenzzonen, Distanz und Kalorien.

Mit sport laesst sich auf eine Sportart filtern, etwa "running".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whoop_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
sportNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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. It discloses that the tool returns strain, heart rate zones, distance, and calories, but does not mention data freshness, pagination, or any constraints such as rate limits or data availability. The transparency is adequate but not thorough.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only two optional parameters and an output schema (not shown but exists), the description covers the main output fields and the filter option. Sibling tools are distinct, so the context is sufficient for an agent to understand when to use this tool.

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 0%, so the description must add meaning. It explains the 'sport' parameter (filtering by sport type like 'running') but does not explain the 'days' parameter beyond its default value of 14. One of two parameters is partially explained, which is helpful but incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool retrieves workouts with specific metrics (Strain, heart rate zones, distance, calories) and mentions the ability to filter by sport. This distinguishes it from sibling tools that deal with recovery, sleep, cycles, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for fetching workout data and filtering by sport, but does not provide explicit guidance on when to use this tool versus siblings like whoop_summary or whoop_recovery. No when-not-to-use or alternative suggestions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools