Skip to main content
Glama
hhopke
by hhopke

icu_update_event

Idempotent

Update an existing calendar event by sending only the fields to change; other fields remain unchanged.

Instructions

Update an existing calendar event.

Only fields you pass are sent — other fields remain unchanged. For category and training_availability semantics, see intervals-icu://event-categories. For WORKOUT description syntax, see intervals-icu://workout-syntax.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent ID to update
nameNoUpdated event name
descriptionNoUpdated description
start_dateNoUpdated start date (YYYY-MM-DD)
event_typeNoUpdated activity type
duration_secondsNoUpdated duration in seconds
distance_metersNoUpdated distance in meters
training_loadNoUpdated training load
end_dateNoUpdated end date (YYYY-MM-DD)
training_availabilityNoUpdated training availability: NORMAL, LIMITED, or UNAVAILABLE
colorNoUpdated color (hex string)
show_as_noteNoShow event as a note on the fitness chart
not_on_fitness_chartNoHide event from the fitness chart
show_on_ctl_lineNoRender event on the CTL line
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?

The description adds a key behavioral detail (partial update) beyond annotations, which already indicate idempotency and non-destructiveness. It does not cover authorization or rate limits, but the added context is valuable.

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 sentences: purpose, key behavior, and pointers to external resources. No redundancy, front-loaded, and every sentence earns its place.

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?

For a complex tool with 15 parameters and partial update semantics, the description covers essential behavioral aspects. With an output schema present, it does not need to detail return values.

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%, so baseline is 3. The description adds value by referencing external documentation for 'category' and 'training_availability' semantics, which aids understanding beyond schema descriptions.

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?

The description clearly states that the tool updates an existing calendar event, distinguishing it from create and delete tools. It uses a specific verb (update) and resource (calendar event), making the purpose explicit.

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 clarifies that only passed fields are changed, which is critical for partial updates. However, it does not explicitly contrast with alternatives like create or delete, though the context of sibling tools makes it clear.

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