Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_create_gear_reminder

Create maintenance reminders for gear items triggered by distance, time, or both to keep equipment serviced on schedule.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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

A3.6/5.0
Behavior3/5

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

Annotations declare write (readOnlyHint=false), non-idempotent, non-destructive, open-world. The description adds that the reminder can be triggered by distance, time, or both, which is behavioral context beyond the annotations. However, it doesn't mention what happens on duplicate creation, permission needs, or whether the reminder is immediately active.

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?

One sentence that front-loads the action and resource, with zero wasted words. The trigger condition is integrated efficiently.

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?

Given the presence of an output schema, the description needn't explain return values. It covers the core purpose and trigger mechanism. Missing usage guidelines and any edge-case behavior, but for a straightforward creation tool with full schema coverage and annotations, it's largely complete.

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 coverage is 100%, so all five parameters are fully described in the schema. The description adds no new parameter meaning beyond the schema; the only added value is the trigger concept, which aligns with the existing distance_alert/time_alert parameters. Baseline 3 is appropriate.

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 (Create) and resource (maintenance reminder for a gear item), and the trigger mechanism (distance, time, or both) distinguishes it from siblings like icu_create_gear or icu_update_gear_reminder. No ambiguity about what the tool produces.

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?

No guidance on when to use this versus icu_update_gear_reminder, nor any note about prerequisites (e.g., gear must exist). The description only says what it does, not when to choose it.

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