Skip to main content
Glama

get_whoop_cycle_recovery

Read-onlyIdempotent

Retrieve recovery data for a specific WHOOP cycle ID to compare daily recovery metrics and support period-based analysis.

Instructions

Retrieve recovery joined to 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_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
cycle_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/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 fully covered by structured data. The description adds only the notion of an 'exact' keyed lookup, which is largely a restatement of the required integer parameter, and says nothing about what happens when a cycle has no recovery record or what the response contains.

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 short sentence with the key constraint ('exact integer cycle ID') placed at the end where it matters. No filler, though the phrasing is terse to the point of being slightly cryptic.

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 one-parameter lookup with no output schema and full annotation coverage, the description covers the essentials of what it fetches. It is incomplete on the two things an agent would still want: how to obtain a cycle_id and whether a missing recovery record yields an error or an empty result.

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 single cycle_id parameter is undocumented in the schema and the description must compensate. 'Exact integer cycle ID' does clarify that the value is a precise identifier rather than a date or range, but it gives no hint on where to source a valid cycle ID.

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 names a specific verb ('Retrieve') and a specific resource ('recovery joined to an exact integer cycle ID'), which is enough to distinguish a single-cycle recovery lookup from siblings like list_whoop_recovery or get_whoop_cycle. It does not explicitly name those siblings, and 'joined' is slightly jargon-y, but the scope is unambiguous.

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 guidance on when to choose this over list_whoop_recovery, get_whoop_cycle, or get_whoop_cycle_sleep, nor any stated prerequisite such as needing a cycle ID obtained from list_whoop_cycles. The agent must infer the use case from the name alone.

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