Polar MCP

Polar Test Results

polar_list_tests

Read-onlyIdempotent

List Polar fitness, orthostatic, and running test results by date range; requires tests:read.

Instructions

List Polar fitness/orthostatic/running test results in a date range. Requires tests: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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds the required auth scope (tests:read), which is genuinely useful context beyond the annotations, but says nothing about pagination, privacy redaction, or the raw-mode escalation requirement.

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 sentences, zero filler, with the resource and scope front-loaded before the permission note. Every clause earns its place.

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?

With an output schema, 90% schema coverage, and full annotations, the description is minimally sufficient. But for a 10-parameter tool offering privacy_mode=raw and include_gps escalation, the absence of any note about the explicit_user_intent gate or the multi-page fetching behavior leaves context the agent must reconstruct from 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 schema already carries the parameter burden (page/limit/all_pages/max_pages/privacy_mode/explicit_user_intent are all described). The description's 'date range' phrasing hints at after/before but adds no format or boundary semantics beyond what the schema states.

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) and a precisely scoped resource (Polar fitness/orthostatic/running test results) bounded to a date range. It is clearly distinguishable from the other polar_list_* siblings, though it never names an alternative or contrast explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the prerequisite 'Requires tests:read', which is useful but not usage guidance in the when-to-use sense. It never says when this tool should be chosen over e.g. polar_list_activity or polar_daily_summary, leaving the agent to infer from the resource name.

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

Deploy Server