Skip to main content
Glama
Sign In
WHOOP MCP

WHOOP MCP

by myke239
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_whoop_day

Read-onlyIdempotent

Retrieves WHOOP recovery, sleep, and training data for a specific local date by joining exact cycles; provide a YYYY-MM-DD date and IANA timezone.

Instructions

Local-date evidence with exact cycle joins. YYYY-MM-DD and IANA timezone required.

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": {
      "calendar_date": "<calendar_date>",
      "timezone": "<timezone>"
    },
    "name": "get_whoop_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneYes
calendar_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds one genuinely useful behavioral note — that the day is resolved on a local date and joined to exact cycles, which hints at timezone-driven boundary handling. It says nothing about what data is returned or any rate/auth constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with no filler, so nothing is wasted, but the brevity tips into under-specification: the leading clause is jargon-heavy and the reader must decode "evidence" and "exact cycle joins" before reaching the concrete format constraints.

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?

For a two-parameter, zero-coverage, no-output-schema tool, the description leaves too much open — it never says which datasets (recovery, sleep, strain, workouts) a day result contains. The cycle-join hint is helpful but does not compensate for the missing scope and return-content information.

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% and both parameters are bare strings, so the description is the only source of format information. It supplies "YYYY-MM-DD" and "IANA timezone," which is valuable, but it does not bind the formats explicitly to parameter names or explain how the timezone shifts the day window.

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

Purpose2/5

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

"Local-date evidence with exact cycle joins" is cryptic phrasing that never states plainly that this returns WHOOP data for one calendar day. The verb is missing entirely (get/list/fetch), and nothing distinguishes it from get_whoop_cycle or list_whoop_cycles beyond the word "day" in the name.

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?

No when-to-use guidance and no mention of any sibling. An agent cannot tell from this text whether to call get_whoop_day, get_whoop_cycle, or summarize_whoop_period for a single-day lookup; only the required-parameter formats are given.

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