Withings MCP Server

get_sleep_summary

Retrieve sleep summary data including duration, deep sleep, REM, wake count, apnea, and breathing disturbances for specified dates.

Instructions

Get sleep summary data (duration, deep sleep, REM, wake up count, breathing disturbances, apnea, etc.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sleep_summary"
  }
}

Input Schema

Name	Required	Description
`startdateymd`	No	Start date in YYYY-MM-DD format
`enddateymd`	No	End date in YYYY-MM-DD format
`lastupdate`	No	Get sleep data modified since this timestamp
`data_fields`	No	Comma-separated list of data fields to include (e.g., 'breathing_disturbances_intensity,apnea_hypopnea_index,snoring,rr_average'). If not specified, returns default fields.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026

addedInput schema / properties / data_fields

Added value: +{
+  "description": "Comma-separated list of data fields to include (e.g., 'breathing_disturbances_intensity,apnea_hypopnea_index,snoring,rr_average'). If not specified, returns default fields.",
+  "type": "string"
+}

First observedDec 20, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided. The description only lists data fields and does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or what happens when no data exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and directly states purpose with examples, though it could be structured slightly better for readability.

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?

The description provides a reasonable list of returned data but lacks explanation of date range behavior, pagination, or handling of missing data. No output schema exists, so description must carry more load.

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 100% with descriptions for all parameters. The description adds examples for data_fields, but overall does not significantly enhance understanding beyond schema.

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 retrieves sleep summary data and lists typical data fields. However, it does not differentiate from sibling tools like get_sleep_details, which may provide more detailed sleep data.

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. No context on required parameters or typical use cases, despite 0 required parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server