WHOOP MCP Server

Overview Schema Source Related Servers Discussions Admin

Get WHOOP cycle by ID

get_cycle_by_id

Retrieve a specific WHOOP physiological cycle using its numeric ID. Use this to fetch detailed strain and recovery data for one cycle from get_cycles results or a recovery record.

Instructions

A single physiological cycle by its numeric 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_cycle_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`cycle_id`	Yes	Numeric cycle id, e.g. from get_cycles or a recovery record

Output Schema

Name	Required	Description
`id`	Yes
`end`	No	Absent while the activity is still in progress
`score`	No
`start`	Yes
`created_at`	Yes
`updated_at`	Yes
`score_state`	Yes
`timezone_offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.7/5.0

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, and it discloses almost nothing. It does not state that this is a read-only fetch, whether authentication is required, whether the result can be empty for an unknown id, or any scoping behavior. Being a plain noun phrase, it adds no behavioral context beyond the schema.

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?

A single front-loaded sentence fragment with zero filler. It is efficient, though it is a fragment rather than a well-formed instruction, which keeps it short of a 5.

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?

With an output schema present, return-format explanation is unnecessary, and the sole parameter is fully covered by the schema. What is missing is the relationship to get_cycles and any note on what 'physiological cycle' returns, leaving a minimal-but-usable definition.

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 100%: cycle_id is documented in the schema with type and an example origin ('from get_cycles or a recovery record'). The description adds nothing beyond that, so the baseline of 3 for schema-covered parameters applies.

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

Purpose3/5

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

The phrase 'A single physiological cycle by its numeric id' identifies the resource and implies a fetch-by-key, but supplies no verb (get/fetch/retrieve) and never names the sibling get_cycles it contrasts with. An agent can infer it is a single-record lookup versus the list tool, but must infer rather than read it.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_cycles. The only implied routing signal is 'single ... by its numeric id', which the agent must extrapolate on its own.

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

Deploy Server