Skip to main content
Glama
Sign In
hhopke

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Get Activities Around

icu_get_activities_around
Read-onlyIdempotent

Fetches activities chronologically before and after a reference activity to answer training-context questions, compare progression, and review what surrounded a race.

Instructions

Fetch the activities chronologically before and after a reference activity (N each side).

Use for "what did I do around this race?", training-context queries, progression comparisons.

Input Schema

NameRequiredDescriptionDefault
countNoNumber of activities before and after
athlete_idNoAthlete ID (for coaches managing multiple athletes)
activity_idYesReference activity ID

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is fully covered. The description adds the useful ordering guarantee ('chronologically before and after') and the symmetric N-per-side window, but says nothing about edge behavior when fewer neighbors exist or how missing/boundary activities are handled.

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 compact blocks: the core behavior first, then usage triggers. Zero filler and nothing the agent must read past to get the essential semantics.

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, rich annotations, and fully documented parameters, the definition covers what an agent needs to select and call it. Only boundary/edge behavior near the start or end of activity history is left implicit.

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% and each parameter (count, athlete_id, activity_id) is self-documented. The description's '(N each side)' reinforces that count is per-direction rather than a total, which is a small but genuine clarification beyond the schema's 'Number of activities before and after'.

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 ('Fetch') and a precisely scoped resource: activities chronologically adjacent to a reference activity, N per side. That scope is unmistakably different from icu_get_recent_activities or icu_get_activities_by_date, though no sibling is named explicitly.

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?

It supplies concrete trigger scenarios ('what did I do around this race?', training-context queries, progression comparisons) that let an agent pattern-match a request to this tool. It stops short of stating when NOT to use it or naming the alternative to pick instead (e.g., date-range or search tools).

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