Skip to main content
Glama
Sign In
withings-mcp

withings-mcp

by partymola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

withings_get_activity

Retrieves daily Withings activity summaries with steps, distance, calories, and active minutes from cache or live API.

Instructions

Get daily activity summaries (steps, distance, calories, active time).

Returns one entry per day from the local cache by default. Run withings_sync first to populate the cache.

Args: start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d". Default: 30 days back from the end date or today, whichever is earlier. end_date: End date as "YYYY-MM-DD", "YYYY-MM" (its last day), or "Nd". Default: today. live: If true, fetch from Withings API instead of cache.

Returns daily activity data sorted by date, with steps, distance in km, calories, and active minutes by intensity level. Not for workout sessions -- use withings_get_workouts instead.

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": "withings_get_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNo
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "withings_get_activityOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the cache-vs-live data source, the sync dependency, the sort order, and the units (distance in km, active minutes by intensity). It does not cover auth requirements, rate limits, or what happens when the cache is empty, which keeps it short of a 5.

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?

Purpose is front-loaded, then source behavior, then Args, then Returns, then the sibling exclusion — a sensible order. The Args block is slightly verbose relative to a 3-parameter tool, but every line adds usable information rather than restating the schema.

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?

No output schema exists, and the description compensates by naming the returned fields, units, and sort order. For a simple read tool with zero required parameters this is nearly complete; only edge-case behavior (empty cache, large-range limits) is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: each of the three parameters gets accepted formats ("YYYY-MM-DD", "YYYY-MM", "30d", "Nd"), interpretation of partial dates (month resolves to its last day), and default resolution rules. This is meaning well beyond the bare typed properties.

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 opening line names a specific verb and resource ("Get daily activity summaries") and enumerates the metrics returned (steps, distance, calories, active time). The closing line explicitly distinguishes it from the workout-session sibling, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a prerequisite ("Run withings_sync first to populate the cache"), a default data source (local cache), and an explicit exclusion with the correct alternative ("Not for workout sessions -- use withings_get_workouts instead"). When-to-use, when-not-to-use, and the alternative are all present.

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

Deploy Server

Other Tools