Skip to main content
Glama
hhopke
by hhopke

icu_bulk_create_events

Create multiple calendar events in one API call, using a JSON array of event objects with required fields like start_date_local, name, and category.

Instructions

Create MANY new calendar events in a single batch call (more efficient than looping create_event).

Accepts a JSON array of event objects, each shaped like an icu_create_event payload. For copying existing events forward use icu_duplicate_events instead — that reuses payloads rather than taking new fields. See intervals-icu://event-categories and intervals-icu://workout-syntax for the referenced enums and DSL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsYesJSON array of event objects. Required per event: start_date_local, name, category. Optional: description, type, moving_time, distance, icu_training_load, end_date_local, training_availability, color, show_as_note, not_on_fitness_chart, show_on_ctl_line. See intervals-icu://event-categories for the category enum and intervals-icu://workout-syntax for WORKOUT `description` syntax.
athlete_idNoAthlete ID (for coaches managing multiple athletes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate write operation, non-destructive, not idempotent. Description adds efficiency context and accepts array payload. No contradictions, but lacks mention of potential partial failures or limits.

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?

Three compact sentences: first states purpose and benefit, second details payload shape, third provides alternatives and references. No wasted words.

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 output schema present and comprehensive annotations, description covers core functionality and alternatives. Could mention error handling or batch limits, but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions. Description adds useful context about payload shape (like icu_create_event) and external references, going beyond schema.

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?

Description clearly states 'Create MANY new calendar events in a single batch call' and contrasts with looping create_event and with icu_duplicate_events for copying.

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?

Explicitly provides when to use (batch creation) and when not to (use icu_duplicate_events for copying) and references external documentation for enums.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hhopke/intervals-icu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server