Skip to main content
Glama

Withings Heart Records

withings_list_heart
Read-onlyIdempotent

List heart rate records from Withings. Supports date range filtering, pagination, and privacy options.

Instructions

List Withings heart records where available. Requires user.metrics scope. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWithings page number.
afterNoOnly return Withings records after this time. Converted to an Withings start_date.
limitNoLocal page-size hint used for pagination safety.
beforeNoOnly return Withings records before this time. Converted to an Withings end_date.
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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as safe, so the description need not repeat that. It adds useful context: scope requirement and a medical disclaimer, but does not describe pagination behavior or data format beyond what annotations imply.

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 at two sentences, with no wasted words. Every sentence serves a purpose: stating the action and noting scope/disclaimer.

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 existence of an output schema and high schema coverage, the description is minimally adequate. However, it lacks usage guidelines and depth on behavioral traits, which would elevate completeness for a tool with 8 parameters.

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?

With schema description coverage at 88%, the input schema already documents most parameters. The description adds no additional parameter meaning or usage hints, so it meets the baseline without exceeding it.

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?

The description clearly states the verb 'List' and resource 'Withings heart records', which distinguishes it from sibling tools like withings_list_activity or withings_list_sleep. However, 'where available' is slightly vague and could be more specific (e.g., 'heart rate measurements').

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 is provided on when to use this tool versus alternatives, such as when heart data might be included in other lists. The only hint is 'Requires user.metrics scope', which is a prerequisite but not a usage criterion.

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