Skip to main content
Glama
Sign In
intervals-icu-mcp

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Fitness Summary

icu_get_fitness_summary
Read-onlyIdempotent

Retrieve an athlete's current fitness, fatigue, and form snapshot (CTL, ATL, TSB, ramp rate) with interpretation and training recommendations to check readiness or overtraining; coaches can specify athlete_id.

Instructions

Get an athlete's current fitness / fatigue / form snapshot — CTL, ATL, TSB, ramp rate, with interpretation and training recommendations.

Use for "how's my form?", "am I overtrained?", training-status checks. Defaults to the authenticated athlete; coaches can pass athlete_id to read one of their managed athletes instead.

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, open-world read, so the description focuses on what the read returns (interpretation and recommendations, not just raw numbers) and on the identity default. That default-to-authenticated-athlete behavior is real context absent from the annotations.

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?

The metric list and the core purpose are front-loaded, followed by usage examples and the one parameter caveat. Every sentence carries information and there is no filler or repetition.

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, return structure need not be explained, and the one optional parameter is fully covered. For the intended training-status use case nothing essential is missing; only a contrast with the sibling fitness-chart tool would make it airtight.

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%, but the description still adds the key semantic that omitting athlete_id reads the authenticated athlete and that coaches supply the id to read a managed athlete. This goes slightly beyond the schema's 'for coaches managing multiple athletes' note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get an athlete's current fitness / fatigue / form snapshot') and enumerates the exact metrics (CTL, ATL, TSB, ramp rate). It does not explicitly distinguish itself from the nearby icu_get_fitness_chart tool, so the agent must infer snapshot-vs-chart.

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?

Provides concrete trigger phrases ('how's my form?', 'am I overtrained?', training-status checks) that map user intent to the tool. It also clarifies the coach vs. self-read case, but never states when to prefer a different tool such as the fitness chart.

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