Skip to main content
Glama

list_whoop_recovery

Read-onlyIdempotent

Retrieve WHOOP recovery records with HRV, resting heart rate, SpO2, and skin temperature by date range to compare daily recovery trends.

Instructions

Page recovery, HRV ms, resting HR bpm, SpO2 % and skin temperature °C.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_whoop_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
limitNo
startNo
next_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes the units of the returned measurements (ms, bpm, %, °C), which is genuine added value, but it says nothing about pagination mechanics, default page size, or how next_token and the date bounds interact.

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 short, front-loaded sentence with no padding; every clause adds a field name and unit. It is efficient, though the fragment lacks an explicit verb, which slightly undercuts immediate clarity.

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 paginated read with a fully-covered safety annotation set and no output schema, the description does enough to convey what data comes back. It falls short on the one area that matters most for a paging tool: how start, end, limit and next_token are meant to be used together.

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% and all four parameters (start, end, limit, next_token) are undocumented in the schema, so the description carries the full burden — and it explains none of them. The word "Page" weakly implies limit/next_token behavior, but no date format for start/end and no paging protocol is given, leaving the agent to guess.

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 description names the resource (recovery) and enumerates the fields returned (HRV, resting HR, SpO2, skin temperature), and the word "Page" hints at a paginated listing. However, it is a noun fragment rather than a verb+resource statement, and it never distinguishes this from siblings like get_whoop_cycle_recovery or list_whoop_cycles, so an agent cannot tell which recovery endpoint to pick from the text alone.

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 exclusions, and no mention of the alternatives among the eight recovery-adjacent sibling tools. The only implied usage cue is "Page," which suggests bulk listing over a range, but nothing states that explicitly or explains when a single-cycle recovery lookup would be preferred.

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