Skip to main content
Glama

Polar Continuous Samples

polar_list_continuous_samples
Read-onlyIdempotent

Retrieve continuous sample records from your Polar device within a given date range. Use pagination to navigate large sets of data.

Instructions

List continuous sample records for a date range. Requires continuous_samples: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
Behavior3/5

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

Annotations already indicate readOnlyHint, destructiveHint false, etc. The description adds permission requirement and 'Not medical advice' disclaimer, but does not elaborate on pagination behavior or other nuances.

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, front-loaded with action and resource. Concise and efficient.

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?

Tool has output schema and annotations cover safety. The description provides permission info but lacks details on pagination or how all_pages works. Mostly sufficient given richness of schema and annotations.

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 88%, so baseline is 3. The description only adds 'date range' which aligns with after/before parameters. No additional parameter semantics beyond the schema.

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 tool lists continuous sample records for a date range, using a specific verb and resource. This distinguishes it from sibling list tools for other resources.

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?

No guidance on when to use this tool versus alternatives, nor when not to use it. The required permission is mentioned but no comparisons to other tools.

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