Polar MCP

Polar Calendar

polar_list_calendar

Read-onlyIdempotent

List Polar calendar entries in a date range to review scheduled training, sleep, or recovery events. Use start and end dates to filter and paginate results.

Instructions

List Polar calendar entries in a date range. Requires calendar:read.

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds the non-obvious authorization requirement (calendar:read), which is real value beyond annotations, but says nothing about the privacy redaction escalation or pagination behavior that the schema only partially conveys.

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?

Two tight sentences with the core action front-loaded and zero filler. It is efficient, though the terseness leaves room for useful detail about the 10-parameter surface.

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 10-parameter tool the description is thin, but an output schema exists, annotations carry the safety profile, and schema coverage is 90%, so most of the burden is already handled elsewhere. The notable gap is that the explicit_user_intent escalation rule tied to privacy_mode=raw is left entirely to the schema.

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 schema already documents date patterns, pagination bounds, and the privacy_mode enum. The description's only parameter-adjacent content is the date-range framing, which adds no syntax or semantics beyond what the schema provides.

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?

States a specific verb (List), resource (Polar calendar entries), and scope (date range), which cleanly separates it from the other polar_list_* siblings that target activities, sleeps, sports, etc. It does not name an alternative or contrast against any sibling, but the resource is unique enough that an agent can place it without opening the schema.

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?

"Requires calendar:read" is a permission prerequisite, not usage guidance. There is no statement of when to pick this tool over related list tools, no mention of how privacy_mode/explicit_user_intent interact, and no exclusions. The agent gets a precondition but no routing advice.

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

Deploy Server