intervals-icu-mcp

Overview Schema Source Related Servers Discussions Admin

Icu Update Activity

icu_update_activity

Idempotent

Modify metadata of an existing activity like name, type, distance, or RPE. Only passed fields are updated; Strava-imported activities cannot be modified.

Instructions

Update an existing activity's metadata (name, type, distance, sub-type, RPE, etc.).

Only fields you pass are sent; everything else stays unchanged. Strava-imported activities cannot be updated. Moving, elapsed and recording time cannot be changed after an activity exists (neither here nor in the web UI); they can only be set when a manual activity is created. Keys passed via fields are sent as-is and are not echoed back in the response.

Input Schema

Name	Required	Description
`feel`	No	How you felt (1-5 scale)
`name`	No	Updated activity name
`race`	No	Mark as race
`tags`	No	Tags; replaces the existing tag list
`fields`	No	Any other writable Activity API field, sent as-is (e.g. {'icu_ignore_hr': true}). Named parameters win on conflict.
`commute`	No	Mark as commute
`trainer`	No	Mark as trainer/indoor workout
`distance`	No	Distance in meters (e.g. for indoor rides whose file lacks it)
`sub_type`	No	Activity sub-type: NONE, COMMUTE, WARMUP, COOLDOWN or RACE
`activity_id`	Yes	Activity ID to update
`description`	No	Updated description
`activity_type`	No	Updated activity type (e.g., Ride, Run, Swim)
`carbs_ingested`	No	Carbohydrates ingested during the session (g)
`perceived_exertion`	No	RPE rating (1-10 scale)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv5.8.0Nov 1, 2026

addedInput schema / properties / carbs_ingested

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Carbohydrates ingested during the session (g)"
+}

addedInput schema / properties / distance

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Distance in meters (e.g. for indoor rides whose file lacks it)"
+}

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Any other writable Activity API field, sent as-is (e.g. {'icu_ignore_hr': true}). Named parameters win on conflict."
+}

addedInput schema / properties / race

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Mark as race"
+}

addedInput schema / properties / sub_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Activity sub-type: NONE, COMMUTE, WARMUP, COOLDOWN or RACE"
+}

addedInput schema / properties / tags

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Tags; replaces the existing tag list"
+}

First observedv0.1.0May 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare idempotent, non-destructive, open-world, but the description adds what they cannot: partial-update semantics ('only fields you pass are sent'), the in-place replacement behavior of list fields implied via fields pass-through, the Strava import restriction, and the fact that keys passed via `fields` are not echoed back in the response.

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 what the tool does, then the partial-update rule, then the constraints. Six tight sentences, none redundant, and the caveats are ordered by likelihood of biting the agent.

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?

With 14 parameters, a real output schema, and full annotation coverage, the remaining burden is behavioral, and the description covers it: partial updates, immutable timing fields, import restrictions, and `fields` pass-through. Nothing an agent needs in order to call it safely 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 per-field meaning is already documented and the description needn't repeat it. It still adds genuine value by explaining the `fields` escape hatch interaction ('sent as-is', named parameters win on conflict) and warning that those keys aren't reflected in the response.

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+resource ('Update an existing activity's metadata') and scopes it with a field list (name, type, distance, sub-type, RPE). The explicit exclusion of moving/elapsed/recording time cleanly separates it from icu_update_activity_streams and the read-only activity tools.

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?

Gives clear when-not guidance: Strava-imported activities cannot be updated, and timing fields can only be set at manual creation. It doesn't name a sibling alternative for the cases it excludes (e.g., which tool to use for streams), so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server