Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Athlete Profile

icu_get_athlete_profile
Read-onlyIdempotent

Retrieve an athlete's profile with FTP, FTHR, pace settings, current CTL/ATL/TSB, and notes; coaches can pass an athlete ID to view managed athletes.

Instructions

Get an athlete's profile — sport settings (outdoor/indoor FTP, FTHR, pace) and current CTL/ATL/TSB.

Also returns the free-text athlete notes (Markdown) when set; change them with icu_update_athlete_notes. 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.8/5.0
Behavior4/5

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

While the annotations handle safety, the description adds valuable context regarding the content returned (notes vs. metrics) and the functional behavior of the default athlete selection.

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 definition is highly concise, front-loading the main purpose and organizing secondary information (like alternatives and default behaviors) efficiently.

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?

Given the breadth of data returned, the description is complete, covering what is retrieved, how options are used, and pointing to the correct sibling tools for modification.

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

Parameters5/5

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

Although the schema covers the technical aspect, the description provides the crucial operational semantics of the `athlete_id`: defaulting to the authenticated user while allowing coaches to specify a managed athlete ID.

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?

The description clearly states the tool's primary function is to retrieve an athlete's profile and lists the specific types of data included, such as sport settings and CTL/ATL/TSB.

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?

It provides excellent guidance by suggesting an alternative tool (`icu_update_athlete_notes`) for related tasks and explains the conditional use of the `athlete_id` parameter for coaches.

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