Skip to main content
Glama
Sign In
WHOOP MCP

WHOOP MCP

by myke239
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_whoop_cycle_sleep

Read-onlyIdempotent

Retrieve the primary sleep record for a specific WHOOP cycle ID to review sleep details tied to that cycle.

Instructions

Retrieve primary sleep for an exact integer cycle ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cycle_id": "<cycle_id>"
    },
    "name": "get_whoop_cycle_sleep"
  }
}

Input Schema

NameRequiredDescriptionDefault
cycle_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one meaningful behavioral detail — that it returns the 'primary' sleep, implying multiple sleep records may exist per cycle — but says nothing about what happens for an invalid ID or an ID with no sleep data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the resource and key constraint appear immediately. It is arguably terse to the point of omitting routing guidance, but nothing in it is wasted.

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

Completeness3/5

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

For a simple single-parameter read tool with full annotations and no output schema, the description is minimally adequate. It leaves unresolved how 'primary sleep' is chosen and how the result differs from get_whoop_sleep, which is the main ambiguity an agent would face.

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 coverage is 0% and the single parameter has no description, so the description carries some burden. 'Exact integer cycle ID' usefully clarifies the identifier type and exact-match semantics, but does not explain where a cycle ID comes from (presumably list_whoop_cycles).

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?

States a specific verb ('Retrieve') and a specific resource ('primary sleep for an exact integer cycle ID'), which distinguishes it from the ID-based sibling get_whoop_sleep. It does not name a sibling explicitly, so the differentiation is inferential rather than stated.

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 on when to choose this over get_whoop_sleep, list_whoop_sleep, or get_whoop_cycle. The only hint is the word 'cycle ID', which implicitly excludes sleep-ID lookups, leaving the agent to infer the routing.

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