Polar MCP

Polar Training Sessions

polar_list_training_sessions

Read-onlyIdempotent

Retrieve Polar training sessions within a start and end date range, with pagination and optional privacy controls for agent-safe analysis.

Instructions

List Polar training sessions in a date range. Requires training_sessions: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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered without the description. The description does add one useful non-annotation fact – the required training_sessions:read scope – but says nothing about pagination behavior, privacy_mode redaction effects, or what the raw escalation entails.

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?

Two short sentences with zero padding; the scope constraint leads and the auth requirement follows. Nothing is repeated from the title or schema.

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?

An output schema exists, so return values need not be described, and the schema is rich at 90% coverage. However, for a 10-parameter tool with a privacy escalation flag and multi-page fetching, the description leaves the agent without any narrative on the raw/explicit_user_intent escalation flow or pagination semantics.

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 schema already documents page, after, before, limit, privacy_mode, and the rest in detail. The description adds no parameter-level meaning (e.g. how privacy_mode interacts with explicit_user_intent or all_pages), so the baseline 3 applies.

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') plus resource ('Polar training sessions') and a scoping constraint ('in a date range'), which distinguishes it from the many other polar_list_* siblings such as polar_list_activity and polar_list_tests. It stops short of explicitly naming a sibling it differs from or clarifying the boundary against those adjacent list tools.

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?

The only guidance is the prerequisite 'Requires training_sessions:read.', which is an auth note rather than a when-to-use rule. There is no indication of when to prefer this over polar_list_activity, polar_list_tests, or polar_list_training_targets, and no exclusions or pagination advice.

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

Deploy Server