Polar MCP

Polar Nightly Recharge

polar_list_nightly_recharge

Read-onlyIdempotent

List Nightly Recharge results for a date range to review recovery trends; supports pagination and privacy controls, and returns summary or structured data. Not medical advice.

Instructions

List Nightly Recharge results in a date range. Requires nightly_recharge:read. Not medical advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Polar page number.
`after`	No	Inclusive start date. Serialized as a Polar date or date-time according to the endpoint contract.
`limit`	No	Local page-size hint used for pagination safety.
`before`	No	Exclusive end date. Serialized as a Polar date or date-time according to the endpoint contract.
`features`	No	Optional Polar v4 feature flags. Values are validated per endpoint; feature ranges that require one day are hydrated safely.
`all_pages`	No	Fetch multiple pages up to max_pages.
`max_pages`	No	Maximum pages to fetch when all_pages is true.
`privacy_mode`	No	Optional per-call privacy override. Defaults to POLAR_PRIVACY_MODE or structured. raw returns upstream Polar JSON. summary removes GPS/map details.
`response_format`	No		markdown
`explicit_user_intent`	No	Required true when privacy_mode=raw or include_gps=true (agent escalation of redaction).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`records`	Yes
`endpoint`	Yes
`has_more`	Yes
`next_page`	No
`privacy_mode`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.5.4Oct 4, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / after / description

Previous value: -"Only return Polar records after this time. Converted to Polar's inclusive from query parameter."New value: +"Inclusive start date. Serialized as a Polar date or date-time according to the endpoint contract."

changedInput schema / properties / before / description

Previous value: -"Only return Polar records before this time. Converted to Polar's exclusive to query parameter."New value: +"Exclusive end date. Serialized as a Polar date or date-time according to the endpoint contract."

addedInput schema / properties / explicit_user_intent

Added value: +{
+  "description": "Required true when privacy_mode=raw or include_gps=true (agent escalation of redaction).",
+  "type": "boolean"
+}

addedInput schema / properties / features

Added value: +{
+  "description": "Optional Polar v4 feature flags. Values are validated per endpoint; feature ranges that require one day are hydrated safely.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / privacy_mode / description

Previous value: -"Optional per-call privacy override. Defaults to POLAR_PRIVACY_MODE or structured. raw returns upstream Polar JSON. summary minimizes sensitive health and profile details."New value: +"Optional per-call privacy override. Defaults to POLAR_PRIVACY_MODE or structured. raw returns upstream Polar JSON. summary removes GPS/map details."

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.3.6Jul 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds the authorization scope requirement and a disclaimer ('Not medical advice'), but does not describe pagination, rate limits, or return behavior, so it adds limited value beyond structured fields.

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?

Three short, front-loaded sentences with no wasted words. Purpose is stated first, followed by the permission requirement and a disclaimer.

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

Completeness4/5

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

Given that an output schema exists and schema coverage is high, the description need not explain return values or parameters in detail. It covers purpose, permission, and a compliance disclaimer, which is sufficient for an agent to invoke it correctly, though mentioning pagination or privacy controls could add marginal value.

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 90%, so the baseline is 3. The description only implies date-range filtering, which is already fully documented in the schema; it adds no additional parameter semantics.

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

Purpose4/5

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

The description uses a specific verb 'List' and resource 'Nightly Recharge results' with scope 'date range', making the purpose clear. It does not explicitly differentiate from siblings like polar_list_sleeps or polar_daily_summary, but the resource is distinct enough.

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?

Only a permission requirement is stated ('Requires nightly_recharge:read'). There is no guidance on when to use this tool versus alternatives, nor any exclusions or contextual cues for selecting it among the many polar_list_* siblings.

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

Deploy Server