Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Wellness Data

icu_get_wellness_data
Read-onlyIdempotent

Retrieve wellness records for a recent date range, defaulting to the last 7 days, to analyze sleep, recovery trends, and weekly summaries.

Instructions

Fetch wellness records over a RANGE of recent days (default last 7).

Use for trends, weekly summaries, "how has my sleep been this week?", recovery curves. For PMC/fitness chart CTL/ATL/TSB series use icu_get_fitness_chart. For a single specific date use icu_get_wellness_for_date instead — this tool always returns a multi-day list.

Input Schema

NameRequiredDescriptionDefault
days_backNoNumber of days to look back
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds behavior beyond that: the default lookback of 7 days and the guarantee that the response is always a multi-day list rather than a single record. It stops short of describing pagination, empty-range behavior, or whether records are sparse for missing days.

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 scope, then use cases, then two explicit alternative routes, in three short sentences with no filler. Every clause either narrows the tool's identity or prevents a sibling misselection.

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?

Two optional params, full schema coverage, rich annotations, and an output schema that carries the return-value detail — so the description only needs to establish scope and routing, which it does. Nothing an agent needs in order to call this correctly is missing.

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%, so both parameters are already documented, and the description only restates the 7-day default. It adds no semantics for athlete_id or for how days_back interacts with data availability, so the schema does the heavy lifting.

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 wellness records') plus the defining scope ('over a RANGE of recent days'), which distinguishes it from the single-date and fitness-chart siblings. An agent can identify the tool's output shape (multi-day list) 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?

Gives concrete use cases ('trends, weekly summaries, "how has my sleep been this week?", recovery curves') and explicitly routes two alternatives: icu_get_fitness_chart for CTL/ATL/TSB series and icu_get_wellness_for_date for a single date. The exclusion ('this tool always returns a multi-day list') closes the main ambiguity.

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