Skip to main content
Glama
Sign In
WHOOP MCP

WHOOP MCP

by myke239
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_whoop_cycle

Read-onlyIdempotent

Retrieve a single physiological cycle by integer ID to review recovery and strain metrics for that cycle.

Instructions

Retrieve one physiological cycle by its integer 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
cycle_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint, so safety behavior is covered. The description adds nothing beyond them: no note on result ordering, missing-ID behavior, or what a 'physiological cycle' actually represents in this API.

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 with no waste. It is efficient, though the brevity leaves the tool under-specified rather than crisp.

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?

With no output schema and an opaque domain term ('physiological cycle'), the description never explains what a cycle covers or what a caller gets back. For a lookup tool returning an undescribed object, an agent has little basis to know the result's shape or usefulness.

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

Parameters2/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 carry the parameter burden. It only restates that cycle_id is an integer, adding no format, range, provenance, or example versus what the schema already declares.

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 concrete verb and resource: retrieve a single physiological cycle. The singular 'one ... by its integer ID' implicitly contrasts with the sibling list_whoop_cycles, so an agent can tell single-fetch from enumeration without opening either schema.

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 explicit when-to-use or when-not-to-use guidance, and no stated alternative. The agent must infer that list_whoop_cycles should be used first to obtain a cycle_id, and nothing says what happens if the ID is invalid or from another source.

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