Loading ToolBench

Reading the current corpus…

whoop-mcp-poke MCP server · D · ToolBench

← Browse

whoop-mcp-poke

github.com/kabirrgrover/whoop-mcp-poke

Model Context Protocol (MCP) server for integrating with WHOOP fitness and health API

2026-07-28+STREAMABLE_HTTP6 tools

52/100

Definition Quality53

Protocol Readiness72

Supportability36

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: stateless requests, Streamable HTTP

Current-spec patterns detected

Summary

Server has 6 tools with basic descriptions and minimal parameter documentation. All tools accept an optional 'date' parameter but lack type constraints, format specifications, and validation guidance. Descriptions are present but generic (avg ~60 chars, below 194-char baseline). No output schemas documented. Error handling returns plain text without recovery guidance. Tools lack idempotency hints and composition support. No tool annotations (readOnlyHint, etc.). Parameter descriptions do not explain format (YYYY-MM-DD) or default behavior clearly enough for LLM reasoning.

Tools (6)

test_connectionread onlysource verified53/100

Test tool to verify MCP server is working.

whoop_get_healthspanread onlyauthsource verified53/100

Get biological age and pace of aging metrics.

whoop_get_overviewread onlyauthsource verified53/100

Get comprehensive Whoop overview data for a specific date.

whoop_get_recoveryread onlyauthsource verified53/100

Get recovery analysis with HRV, RHR, and trends.

whoop_get_sleepread onlyauthsource verified53/100

Get detailed sleep analysis and performance metrics.

whoop_get_strainread onlyauthsource verified53/100

Get strain analysis with heart rate zones and activities.

Issues (5)

CRITICALresponse-shaper ↗

No output schemas documented. Tools return plain text strings without structured field definitions. LLMs cannot plan downstream calls or extract typed data.

whoop_get_overviewwhoop_get_sleepwhoop_get_recoverywhoop_get_strainwhoop_get_healthspan

HIGHconstrained-input ↗

Parameter 'date' lacks format specification and validation guidance. Description says 'optional, defaults to today' but does not state YYYY-MM-DD is required, what happens if format is wrong, or how the default is applied.

whoop_get_overviewwhoop_get_sleepwhoop_get_recoverywhoop_get_strainwhoop_get_healthspan

HIGHrecovery-guide ↗

Error responses return plain text ('Error fetching Whoop overview data: {error_msg}') without recovery guidance. LLM cannot determine if error is retryable, user-fixable, or fatal.

whoop_get_overviewwhoop_get_sleepwhoop_get_recoverywhoop_get_strain

Recommendations

Add explicit output schemas to all tools. Document returned fields (e.g., 'Returns object with fields: sleep_duration (number, minutes), sleep_quality (string: poor|fair|good|excellent), timestamp (ISO 8601 string)').
Enhance 'date' parameter description: 'Date in YYYY-MM-DD format (e.g., 2024-01-15). Optional; defaults to today. Invalid format returns error with example.'
Implement structured error responses with error codes and recovery hints: '{"error": "invalid_date_format", "message": "Date must be YYYY-MM-DD", "recovery": "Try format like 2024-01-15"}'.
Add tool annotations via FastMCP: mark all tools with readOnlyHint=true and idempotentHint=true to signal safety to agents.
Document authentication and permission model: which scopes are required, how credentials are injected, and what audit logging is in place.

Score history

Overall score trend

First recorded score · v2 rubric

52/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	52	2026-07-28+	v2