Skip to main content
Glama
yuridivonis

Whoop MCP Server

by yuridivonis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Strain history

get_strain_history
Read-onlyIdempotent

Retrieve daily WHOOP strain, calories, heart rate, and steps for recent days to track overall activity load and trends; today is marked and pending days are noted.

Instructions

Returns daily strain for the last days days (default 14), including today so far, newest first, as a Markdown table: WHOOP day strain (0–21, covering all activity that day), calories burned (kcal), average and max heart rate and steps, then averages; the day in progress is marked and left out of the averages. Days WHOOP hasn't scored yet are listed as pending. Use it for overall load and activity trends. For individual training sessions, use get_workouts; for how the body coped, use get_recovery_trends. 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.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context beyond them: live fetch on every call with no cached copy, un-scored days listed as pending, the in-progress day marked and excluded from averages, and a fallback path (returning a message to call get_auth_url) when WHOOP is not connected. This is exactly the behavioral disclosure annotations cannot carry.

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?

Front-loaded with the return shape and followed by usage, alternatives, and failure modes in a logical order. It is a dense paragraph rather than bullets, and a few clauses (e.g., repeating the day-range guidance already implied by the parameter) could be trimmed, but nearly every sentence earns its place.

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?

With no output schema, the description fully compensates by enumerating the returned columns (strain, calories, avg/max HR, steps, averages), the row ordering, the pending/in-progress markers, and the error/not-connected behaviors. An agent has everything needed to call it and interpret the result.

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 coverage is 100%, so the baseline is 3, and the schema already documents range (1-90) and default. The description goes further by mapping intent to value ('7 for the last week, 30 for the last month'), which is meaningful guidance beyond the schema's numeric bounds.

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+resource (daily strain history), the exact scope (last `days` days, default 14, including today), and the return shape (Markdown table, newest first). It also distinguishes itself from siblings by naming get_workouts and get_recovery_trends as the alternatives for their respective questions.

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 routes the agent: 'Use it for overall load and activity trends. For individual training sessions, use get_workouts; for how the body coped, use get_recovery_trends.' It further gives concrete parameter selection guidance (7 for the last week, 30 for the last month, up to 90).

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