Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Create Gear Reminder

icu_create_gear_reminder

Creates a maintenance reminder for a gear item, triggering alerts by distance, time, or both.

Instructions

Create a maintenance reminder for a gear item, triggered by distance, time, or both.

Input Schema

NameRequiredDescriptionDefault
textYesReminder text (e.g., 'Replace chain', 'New shoes')
gear_idYesID of the gear item
athlete_idNoAthlete ID (for coaches managing multiple athletes)
time_alertNoAlert every N hours (e.g., 100 for every 100 hours)
distance_alertNoAlert every N kilometers (e.g., 500 for every 500km)

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=false, destructiveHint=false and openWorldHint=true, so the mutation and safety profile is covered. The description contributes the trigger semantics (distance, time, or both), but says nothing about duplicate-reminder behavior, whether a reminder with no alert is valid, or permission/auth needs for coach-scoped writes. Adequate but thin against a lowered bar.

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?

A single sentence with no filler, front-loading the verb and resource followed by the one non-obvious behavioral detail. Nothing is wasted.

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, annotations covering the safety profile, and full schema descriptions for all five parameters including the coach-facing athlete_id, the agent has enough to call this correctly. The remaining gap is the missing relationship to the update sibling, which is a routing concern rather than a completeness failure for the call itself.

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%, including worked examples for text, time_alert, and distance_alert, so the schema already does the heavy lifting. The description's 'distance, time, or both' confirms the two alert parameters are combinable, which is marginal added meaning. 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?

The description names a specific verb and resource — 'Create a maintenance reminder for a gear item' — and adds the trigger model (distance, time, or both), which is the core semantics of the resource. It does not explicitly distinguish itself from the sibling icu_update_gear_reminder, so it falls short of a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative (icu_update_gear_reminder) or of what happens if a reminder already exists. The only usage signal is implicit in the trigger wording.

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