Skip to main content
Glama
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

icu_get_gear_list

Read-onlyIdempotent

Fetch all gear items with usage stats—distance, time, activity count—and maintenance reminders. Optionally specify an athlete ID for coaches managing multiple athletes.

Instructions

List all gear items with usage stats (distance, time, activity count) and maintenance reminders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
athlete_idNoAthlete ID (for coaches managing multiple athletes)

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without description help. The description adds that the result includes derived usage stats and maintenance reminders, which is useful content disclosure, but says nothing about pagination, caching, or how far back the stats aggregate.

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, front-loaded with the verb and resource and with the return contents in a tight parenthetical. Nothing is wasted or buried.

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?

An output schema exists, so return-value detail is not required, and the single optional parameter is documented in the schema. The description is nearly sufficient; the only missing nuance is the coach/multi-athlete scoping behavior of omitting athlete_id.

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% for the single optional athlete_id parameter, so the schema carries this dimension. The description contributes nothing about the parameter and its use of 'all gear items' slightly undersells that results are scoped when athlete_id is supplied; 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 ('List') and resource ('all gear items') and enumerates the payload (distance, time, activity count, maintenance reminders), so an agent knows exactly what comes back. It doesn't explicitly differentiate itself from near siblings like icu_create_gear or icu_update_gear, but the read-only list intent is unambiguous.

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 statement of when to reach for this tool versus alternatives (e.g. icu_get_custom_items, gear-reminder tools), and no mention of the optional athlete_id scoping for coaches. Usage is only implied by the word 'List'.

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