Skip to main content
Glama

Withings Sleep Detail

withings_list_sleep
Read-onlyIdempotent

Retrieve detailed sleep records from Withings, with pagination and date range filtering. Control output privacy using summary, structured, or raw formats.

Instructions

List detailed Withings sleep data where available. Requires user.activity scope. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWithings page number.
afterNoInclusive start bound. Converted to Withings startdate (epoch) or startdateymd (YYYY-MM-DD) per action.
limitNoUpstream page-size hint and local output cap used for pagination safety.
beforeNoInclusive end bound. Converted to Withings enddate (epoch) or enddateymd (YYYY-MM-DD) per action.
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 WITHINGS_PRIVACY_MODE or structured. raw returns upstream Withings 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 provide read-only, idempotent, and non-destructive hints. The description adds value by disclosing the scope requirement and that output is not medical advice, which are useful behavioral traits 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?

Three short sentences with no redundancy: purpose, scope requirement, disclaimer. Each sentence 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?

Given the presence of an output schema and rich annotations, the description is adequate for basic understanding. However, it could mention the sibling summary tool for comparison, and the parameter count (8) suggests the description might underspecify when detailed data is available.

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 coverage is 88%, so parameters are already well-described. The overall description adds no extra parameter-specific meaning beyond stating 'detailed sleep data', which is implied by the schema and tool name.

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' and specific resource 'detailed Withings sleep data'. It distinguishes from the sibling 'withings_list_sleep_summary' by implying detail, and adds scope requirement and disclaimer.

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 includes a required scope ('user.activity scope') but does not explicitly guide when to use this tool versus alternatives such as the summary sibling. Usage context is partly clear but lacks explicit exclusions or when-not-to-use guidance.

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/withings-mcp'

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