Skip to main content
Glama

Withings Workouts

withings_list_workouts
Read-onlyIdempotent

Retrieve a list of Withings workouts with optional date filtering and pagination. Requires user.activity scope.

Instructions

List Withings workouts. Requires user.activity scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWithings page number.
afterNoOnly return Withings records after this time. Converted to Withings startdate.
limitNoUpstream page-size hint and local output cap used for pagination safety.
beforeNoOnly return Withings records before this time. Converted to Withings enddate.
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?

The description adds a behavioral requirement (user.activity scope) beyond the annotations, which already indicate read-only, idempotent, non-destructive behavior. This concrete scope information aids the agent in understanding prerequisites.

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 two sentences, containing only essential information: the tool's action and a required scope. No fluff, perfectly concise for the given complexity.

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 complexity of 8 parameters and the presence of an output schema and rich annotations, the description is minimal. It does not explain return values or pagination, though the schema compensates. Adequate but not fully comprehensive.

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 88% schema description coverage, the schema already documents most parameters. The description adds no extra parameter semantics beyond the tool's purpose, so a baseline score of 3 is appropriate.

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 tool lists Withings workouts, using a specific verb and resource. However, it does not differentiate from sibling tools like withings_list_activity, leaving ambiguity about what constitutes a workout.

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 given on when to use this tool versus alternatives (e.g., withings_list_activity). The only context is the required scope, but no usage scenarios or exclusions are provided.

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