Vitalli

vitalli_get_daily_metrics

Read-onlyIdempotent

Get the signed-in user's daily wearable values from the Vitalli hub, one entry per day, newest first: sleep score, total sleep, efficiency, deep, REM and light sleep, awake time, sleep latency, time in bed and bed times; readiness score, resting heart rate, average night heart rate, HRV, respiratory rate, SpO2 and skin temperature deviation; steps, active calories and activity score. Each day names its primary device (Oura, Polar, Garmin, Apple Health or Withings, preferred in that order; provider apple_health is the Apple Watch and other apps writing to Apple Health), lists fields that came from another device in fieldSources, and carries syncedAt. hrvMethod says what hrvMs is: rmssd (Oura, Polar, Garmin) or sdnn (Apple Health); the two are not comparable. latestNight is the newest day in the range with sleep data, devices lists the connected devices with their last sync. Fields a device does not measure are null; Apple Health has no sleep score, so sleepScore is null there. Sleep stages and bed times exist for Oura, Garmin and Apple Health. Days are calendar days in Europe/Berlin, a night counts for the morning it ended. Values are device measurements and the providers' own scores, not a medical assessment.

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

Input Schema

Name	Required	Description	Default
`date`	No	Last day of the range (YYYY-MM-DD), the morning the night ended. Default: today in Europe/Berlin.
`days`	No	Number of days up to and including date, 1 to 31. Default 7.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond that: per-device null semantics, Apple Health having no sleep score, hrvMethod making rmssd and sdnn non-comparable, fieldSources and syncedAt on each day, and the Europe/Berlin calendar-day rule. It even disclaims that values are device measurements, not medical assessment.

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?

Front-loaded with the core purpose and field list, and nearly every clause carries real information (device preference order, hrvMethod, null behavior). The downside is a single dense paragraph with semicolon-chained field lists, which is harder to scan than a short structured list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description has to carry the return-value burden, and it does: it describes the entry shape (day, primary device, fieldSources, syncedAt), the auxiliary keys (latestNight, devices, hrvMethod), and the device-specific null cases. An agent has enough to interpret the response correctly.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented; the description adds the calendar-day interpretation ('a night counts for the morning it ended') and the timezone anchoring, which reinforce the `date` semantics. It does not add anything for `days` beyond the schema's 1-31 bound and default 7.

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?

States a specific verb and resource ('Get the signed-in user's daily wearable values from the Vitalli hub, one entry per day, newest first') and then enumerates the exact metric families returned. That granularity distinguishes it from siblings like vitalli_get_health_profile or vitalli_get_longevity without the agent needing to open a schema.

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?

Usage is implied rather than stated: the agent can infer this is the tool for per-day wearable values, and the mention of 'latestNight is the newest day in the range with sleep data' hints at range semantics. But there is no explicit when-to-use/when-not guidance and no routing to alternatives such as vitalli_get_health_profile for profile data.

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

All Vitalli tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?