Skip to main content
Glama

Polar User Devices

polar_list_user_devices
Read-onlyIdempotent

Retrieve a list of devices registered to your Polar account. Filter by time range and pagination options.

Instructions

List devices registered to the Polar user. Requires devices:read.

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?

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the authorization requirement 'Requires devices:read', providing useful context beyond 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?

Two efficient sentences cover the essential purpose and authorization without unnecessary words, maximizing readability for an AI agent.

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?

The description is complete enough for a straightforward listing tool, covering authorization and core purpose. The output schema exists to detail return values, so no further elaboration is needed.

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 the schema already documents parameters well. The description adds no further parameter detail, meeting the baseline but not exceeding it.

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 it lists devices registered to the Polar user, using a specific verb and resource. It distinguishes from sibling list tools by focusing on the unique resource of devices.

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 implies use for listing user devices but lacks explicit guidance on when not to use it or alternatives, making it adequate but not exemplary.

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