Skip to main content
Glama
yuridivonis

Whoop MCP Server

by yuridivonis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Recovery trends

get_recovery_trends
Read-onlyIdempotent

Compare daily recovery, HRV, and resting heart rate over any period up to 90 days. Get live averages in a table to spot patterns and track changes.

Instructions

Returns daily recovery for the last days days (default 14), newest first, as a Markdown table: recovery score (%), HRV (ms) and resting heart rate (bpm) for each of the user's local days, then averages. Days WHOOP hasn't scored are left out. Use it for patterns and comparisons, such as "how has my HRV changed this month?". For today alone, use get_today; for the sleep behind the numbers, use get_sleep_analysis. Set days to match the question: 7 for the last week, 30 for the last month, up to 90. Read-only: it never changes the user's WHOOP data. It fetches the data live from WHOOP on every call and keeps no copy, so the answer is current; if WHOOP can't be reached, it says so. If WHOOP isn't connected yet, it returns a message asking to call get_auth_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days to cover, counting back from today: 1 to 90, default 14.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.2
    • addedInput schema / properties / days / default
      Added value: +14
    • changedInput schema / properties / days / description
      Previous value: -"Number of days to analyze (default: 14, max: 90)"New value: +"How many days to cover, counting back from today: 1 to 90, default 14."
    • addedInput schema / properties / days / maximum
      Added value: +90
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial behavioral context beyond annotations: live fetching on every call, no caching, error handling ('if WHOOP can't be reached, it says so'), and auth requirement (asks to call get_auth_url if not connected). Also notes missing days are skipped. These details are not in annotations and materially affect how an agent interprets results. No contradiction with the readOnly/readOnlyHint annotations.

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 dense but every sentence earns its place: it front-loads the core purpose and output, then covers usage examples, alternatives, parameter guidance, and behavioral details. No fluff or repetition; it reads naturally and logically.

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

Completeness5/5

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

Covers all essential aspects for a simple list tool: output format, default, range, filtering of unscored days, error handling, auth flow, and sibling routing. There is no output schema, but the description fully describes the return value. Given the low parameter count and clear annotations, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already fully documents 'days' (range and default). The description adds value by mapping typical values to real-world periods ('7 for the last week, 30 for the last month, up to 90'), which aids correct selection. Since schema coverage is 100%, baseline is 3, but the contextual mapping lifts it to 4.

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?

States a specific verb ('Returns') and resource ('daily recovery') with clear output format (Markdown table with scores, HRV, RHR). It explicitly differentiates from siblings by naming get_today and get_sleep_analysis with their use cases, so an agent can distinguish without opening other schemas.

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

Usage Guidelines5/5

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

Explicitly tells when to use it ('for patterns and comparisons'), provides concrete examples ('how has my HRV changed this month?'), and gives when-not-to-use alternatives ('For today alone, use get_today; for the sleep behind the numbers, use get_sleep_analysis'). Also gives parameter selection guidance for days (7/30/90) matching the time window.

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