Skip to main content
Glama
MadLlama25

Fastmail MCP Server

by MadLlama25

update_calendar_event

Modify an existing calendar event: update only specified fields (title, time, location, description, participants) while preserving others. Replace or clear attendees via the participants parameter.

Instructions

Update an existing calendar event. Preserves all existing data (attendees, reminders, recurrence rules, etc.) not being changed. Omit a field to leave it unchanged; passing an empty/whitespace string for title, description, or location is rejected (use clearFields to delete description/location). Floating times preserve the original timezone; explicit UTC/offset times convert to UTC. WARNING: providing participants replaces ALL existing attendee data (acceptance status, roles, etc.). participants: [] removes all attendees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoNew end time in ISO 8601 format. DTEND is exclusive per RFC 5545
startNoNew start time in ISO 8601 format. Floating times (no Z/offset) preserve original timezone
titleNoNew event title
eventIdYesID of the event to update
locationNoNew event location
clearFieldsNoProperty names to delete from the event. Allowed: description, location. Cannot also pass the same field as a value.
descriptionNoNew event description
participantsNoReplaces ALL existing attendees. Empty array removes all attendees. Omit to preserve existing attendees.
confirmRecurringNoRequired when changing start/end on a recurring event with exceptions. Acknowledges that orphaned exception overrides will be removed.
Behavior5/5

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

No annotations are provided, so the description carries full burden. It fully discloses key behaviors: preserving unchanging fields, rejecting empty strings for title/description/location, timezone handling, participant replacement, and the effect of clearFields. This is comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph that is concise but dense. It is front-loaded with the core purpose. While effective, it could benefit from bullet points for improved readability.

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?

Given the tool has 9 parameters and no output schema, the description covers essential behaviors and warnings. It provides enough context for correct invocation, though some details about response or error states are omitted.

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 significant value beyond schema by explaining timezone behavior, participant replacement semantics, and clearFields constraints. This justifies an above-baseline score.

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 states 'Update an existing calendar event' with a specific verb and resource. It clearly distinguishes from sibling tools like create_calendar_event and delete_calendar_event.

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?

The description explains when to use the tool (e.g., for updating events) and provides warnings against misuse, such as the need for confirmRecurring on recurring events. However, it does not explicitly list alternative tools for specific scenarios.

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/MadLlama25/fastmail-mcp'

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