Skip to main content
Glama

Polar Sleeps

polar_list_sleeps
Read-onlyIdempotent

Retrieve sleep records from Polar devices within a specified date range. Supports pagination and privacy controls for health data.

Instructions

List Polar sleep records in a date range. Requires sleep:read. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPolar page number.
afterNoOnly return Polar records after this time. Converted to Polar's inclusive from query parameter.
limitNoLocal page-size hint used for pagination safety.
beforeNoOnly return Polar records before this time. Converted to Polar's exclusive to query parameter.
all_pagesNoFetch multiple pages up to max_pages.
max_pagesNoMaximum pages to fetch when all_pages is true.
privacy_modeNoOptional per-call privacy override. Defaults to POLAR_PRIVACY_MODE or structured. raw returns upstream Polar JSON. summary minimizes sensitive health and profile details.
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
recordsYes
endpointYes
has_moreYes
next_pageNo
privacy_modeYes
pages_fetchedYes
Behavior4/5

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

The description adds value beyond annotations by stating the required authorization scope 'sleep:read' and the disclaimer 'Not medical advice'. It does not contradict any annotations.

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?

The description is extremely concise, consisting of three short sentences, each providing essential information. It is front-loaded with the core purpose.

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 the presence of an output schema and detailed parameter descriptions, the description provides adequate completeness by adding authorization requirements and a disclaimer. It covers the key contextual points.

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 high (88%), so the baseline is 3. The description does not add significant meaning beyond the schema's parameter descriptions.

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

Purpose5/5

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

The description clearly states the verb 'List', the resource 'Polar sleep records', and the scope 'in a date range'. It distinguishes from sibling tools by specifying 'sleep records', which is not used by any other sibling tool.

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 description mentions the required authorization scope 'sleep:read', which provides some context for when the tool can be used, but it does not compare to alternative tools or specify when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/polar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server