Skip to main content
Glama
intervals-icu-mcp
by hhopke

Icu Update Athlete Notes

icu_update_athlete_notes
Idempotent

Replace the free-text notes on an athlete’s profile to maintain standing context such as injuries, while keeping activity comments and calendar notes separate.

Instructions

REPLACE the free-text notes kept on an athlete's own record — not an activity comment or a calendar note.

Use for standing context about the athlete: "note on my profile that I'm injured", "update my athlete notes". The whole text is overwritten, so to add to existing notes read them first with icu_get_athlete_profile and send the combined text. For a comment on one activity use icu_add_activity_message; for a dated calendar note use icu_create_event.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notes": "<notes>"
    },
    "name": "icu_update_athlete_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYesFull new notes text (Markdown). Replaces the existing notes; pass an empty string to clear them.
athlete_idNoAthlete ID (for coaches managing multiple athletes)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.7.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=true, destructive=false; the description supplies the critical operational fact the annotations cannot: the whole text is overwritten, so prior content is lost unless re-supplied. It also provides the mitigation workflow (read-first) and the clearing behavior, which is exactly the beyond-annotation context an agent needs.

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-loaded with the mutation type in caps, then usage examples, then the overwrite caveat, then sibling routing. Four short sentences and a fragment, every one carrying distinct decision-relevant information.

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?

Covers what the tool writes, when to select it, when to select siblings instead, the data-loss risk of the replace semantics, and the read-modify-write pattern. With an output schema present, no return-value explanation is needed, so nothing material 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; the description adds genuine meaning by framing the notes parameter as full-replacement standing context rather than an append, and by tying the clearing case to the overwrite semantics. It says nothing extra about athlete_id (coach use case), which stays entirely in the schema.

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 ('REPLACE the free-text notes kept on an athlete's own record') and immediately negates the two nearest lookalikes ('not an activity comment or a calendar note'). An agent can distinguish this from icu_add_activity_message and icu_create_event without opening a 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 explicit natural-language triggers ('note on my profile that I'm injured', 'update my athlete notes') and names both alternatives with the condition that routes to them: activity comment vs dated calendar note. It even prescribes the prerequisite workflow (read with icu_get_athlete_profile, then send combined text).

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