intervals-icu-mcp

Overview Schema Source Related Servers Discussions Admin

icu_update_wellness

Idempotent

Create or update wellness data for a single date, covering HRV, sleep, weight, mood, and fatigue. Send only the fields you want to change.

Instructions

Upsert wellness data for ONE specific date — creates the record if missing, otherwise updates the fields you pass.

Only provided fields are sent. Subjective scales (fatigue, soreness, stress, mood, motivation, injury) are 1-5. Pass locked=True to stop device sync from overwriting manual entries. Writes to the authenticated athlete unless athlete_id names a managed athlete.

Input Schema

TableJSON Schema

Name	Required	Description
`hrv`	No	HRV (rMSSD) value
`date`	Yes	Date in YYYY-MM-DD format
`mood`	No	Mood level (1-5 scale)
`spo2`	No	Blood oxygen saturation percentage (SpO2)
`injury`	No	Injury severity (1-5 scale: 1=none, 5=severe)
`locked`	No	Lock record to prevent device sync from overwriting manual entries
`stress`	No	Stress level (1-5 scale)
`vo2max`	No	VO2max (ml/kg/min) — lab result or device estimate
`weight`	No	Weight in kg
`abdomen`	No	Abdominal circumference in cm
`fatigue`	No	Fatigue level (1-5 scale)
`lactate`	No	Blood lactate in mmol/L — lab result
`protein`	No	Protein consumed (grams)
`body_fat`	No	Body fat percentage
`comments`	No	Comments or notes
`soreness`	No	Soreness level (1-5 scale)
`systolic`	No	Systolic blood pressure in mmHg
`diastolic`	No	Diastolic blood pressure in mmHg
`fat_total`	No	Total fat consumed (grams)
`hydration`	No	Subjective hydration rating (1-4: 1=well hydrated, 4=very dehydrated)
`readiness`	No	Readiness score (0-100)
`athlete_id`	No	Athlete ID (for coaches managing multiple athletes)
`motivation`	No	Motivation level (1-5 scale)
`resting_hr`	No	Resting heart rate in bpm
`sleep_secs`	No	Sleep duration in seconds
`respiration`	No	Respiration rate in breaths per minute
`blood_glucose`	No	Blood glucose in mmol/L
`carbohydrates`	No	Carbohydrates consumed (grams)
`sleep_quality`	No	Sleep quality (1-5 scale)
`menstrual_phase`	No	Menstrual phase (e.g. FOLLICULAR, OVULATING, LUTEAL, MENSTRUAL)
`hydration_liters`	No	Hydration volume (liters)
`calories_consumed`	No	Calories consumed (kcal)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv5.0.1Sep 11, 2026

addedInput schema / properties / athlete_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Athlete ID (for coaches managing multiple athletes)"
+}

addedInput schema / properties / hydration

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Subjective hydration rating (1-4: 1=well hydrated, 4=very dehydrated)"
+}

First observedv0.1.0May 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real behavior beyond annotations: upsert semantics (creates or updates), partial-update behavior (only provided fields sent), the effect of locked on device sync overwriting, and athlete targeting. This complements the idempotentHint/destructiveHint annotations rather than repeating them, though it doesn't cover permission/error behavior.

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?

Front-loads the core upsert contract in the first sentence, then layers the field-scales rule, the locked behavior, and athlete targeting with zero filler. Every sentence earns its place.

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?

For a 32-param mutation tool with an output schema present, the description covers the crucial unknowns: create-vs-update semantics, partial writes, lock interaction with device sync, and target-athlete resolution. Return values are covered by the output schema, so nothing essential is missing.

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 baseline is 3, but the description adds useful grouping, calling out which fields are subjective 1-5 scales and explaining the locked flag's purpose in driving sync behavior. It slightly exceeds what the schema alone conveys for the key semantic fields.

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 (upsert) and resource (wellness data) scoped to ONE specific date, and immediately disambiguates the create-vs-update behavior. This clearly separates it from sibling read tools like icu_get_wellness_data and icu_get_wellness_for_date.

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

Usage Guidelines4/5

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

Gives clear context: single-date upsert, only provided fields are sent, and the locked=True condition for protecting manual entries. It does not explicitly name the read alternative (icu_get_wellness_for_date) it should be contrasted with, but the usage context is unambiguous.

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

Deploy Server