Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Wellness For Date

icu_get_wellness_for_date
Read-onlyIdempotent

Fetches the wellness record for a single specified date, so you can check HRV, sleep, and related metrics when a user names one day.

Instructions

Fetch the wellness record for ONE specific date.

Use when the user names a date — "show my HRV for Monday", "wellness on 2026-03-15", "how did I sleep last Thursday?". For ranges, weeks, or trends use icu_get_wellness_data.

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
athlete_idNoAthlete ID (for coaches managing multiple athletes)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / athlete_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Athlete ID (for coaches managing multiple athletes)"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without the description. The description's only added behavioral signal is the single-date scope, which is useful but thin; it says nothing about what happens when no record exists for that date.

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?

Two short blocks: the scope statement is front-loaded, then the routing rule and quoted examples. Every sentence carries a distinct piece of information with no repetition of the name or title.

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?

With an output schema present and only two fully documented parameters, the description covers everything needed to select and invoke the tool. The remaining gap is minor: no guidance on missing/empty wellness data for the requested date.

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 the baseline would be 3, but the description earns above baseline by showing that users may express the date loosely ('Monday', 'last Thursday'), signalling the agent must resolve natural-language dates to the schema's YYYY-MM-DD format. It says nothing about athlete_id, though the schema documents that at 100%.

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 ('Fetch the wellness record') plus a hard scope constraint ('for ONE specific date'). The emphasis on 'ONE' immediately separates it from the range-oriented sibling icu_get_wellness_data.

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?

Gives explicit when-to-use triggers with three realistic user phrasings ('show my HRV for Monday', 'wellness on 2026-03-15', 'how did I sleep last Thursday') and names the alternative for ranges/weeks/trends. Nothing is left to inference about routing.

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