Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Update Gear Reminder

icu_update_gear_reminder
Idempotent

Update an existing gear maintenance reminder by changing its text, distance alert, or time alert; only the fields you provide are modified.

Instructions

Update an existing gear maintenance reminder. Only fields you pass are sent.

Input Schema

NameRequiredDescriptionDefault
textNoUpdated reminder text
gear_idYesID of the gear item
athlete_idNoAthlete ID (for coaches managing multiple athletes)
time_alertNoUpdated time alert in hours
reminder_idYesID of the reminder to update
distance_alertNoUpdated distance alert in kilometers

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely useful partial-update semantics ('Only fields you pass are sent'), but does not explain how nulls behave (e.g. whether passing null clears an alert), which matters given every optional field accepts null.

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?

Two sentences, zero waste, and the operational constraint (partial update) is front-loaded right after the purpose statement.

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?

Output schema exists and annotations cover the safety profile, so the description needn't explain returns. What it lacks is null/clear semantics for the nullable alert fields, which is the one real gap for a patching tool.

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 description coverage is 100%, so all six parameters are already documented in the schema. The description adds only the patch-semantics framing rather than per-parameter meaning, so baseline 3 applies.

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 and resource: 'Update an existing gear maintenance reminder'. This distinguishes it implicitly from icu_create_gear_reminder and icu_update_gear, though it doesn't name those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'existing' hints that this is for reminders already created, but there is no explicit when-to-use guidance, no mention of when to prefer icu_create_gear_reminder vs this tool, and no prerequisites such as required permissions or whether the reminder must belong to the given gear/athlete.

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