Skip to main content
Glama
Sign In
intervals-icu-mcp

intervals-icu-mcp

by hhopke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Icu Search Activities Full

icu_search_activities_full
Read-onlyIdempotent

Search activities by name or tag and return complete Activity objects with power, heart rate, training load, intensity factor, normalized power, and weather metrics for detailed ride analysis.

Instructions

Search activities by name or tag, returning FULL Activity objects with power, HR, training load, intensity factor, normalized power, weather — every metric per result.

Heavy payload. Use only when the lighter search_activities won't tell you what you need (e.g. "find my threshold rides with NP above 250W").

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return
queryYesSearch query (activity name or tag)
athlete_idNoAthlete ID (for coaches managing multiple athletes)

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

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely useful context the annotations cannot convey: the payload is heavy and the response is fully hydrated per-result. It stops short of mentioning pagination or default result-count behavior, which keeps it from a 5.

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 short blocks with zero filler: the capability plus return payload first, then the cost/alternative guidance. The heavy-payload warning is placed before the usage rule so the agent sees the tradeoff in the right order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values needn't be enumerated, yet the description still summarizes the payload's richness and its cost. Combined with the explicit sibling routing, an agent has everything needed to call this correctly and to know when not to.

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 query, limit, and athlete_id are already documented in the input schema. The description's "by name or tag" adds only marginal color about what the query matches, and says nothing about limit or the coach-scoped athlete_id. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ("Search activities by name or tag") plus the distinctive return shape: FULL Activity objects with power, HR, training load, NP, weather. It explicitly contrasts with the sibling icu_search_activities, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not ("Use only when the lighter search_activities won't tell you what you need") and names the alternative, backed by a concrete example query ("find my threshold rides with NP above 250W"). Both the selection rule and its motivating case are present.

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