Skip to main content
Glama
Sign In
Infomaniak Calendar MCP Server

Infomaniak Calendar MCP Server

Official
by Infomaniak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

calendar_delete_event

Delete an Infomaniak calendar event by event ID, optionally from a specified calendar and with cancellation emails sent to attendees. Use it to remove unwanted events via the API.

Instructions

Delete an Infomaniak calendar event

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "calendar_delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesThe ID of the event to delete
calendar_idNoCalendar ID (optional, uses default if not provided)
notify_attendeesNoSend a cancellation to attendees via email (imip). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden but discloses almost nothing: it does not state that deletion is permanent, what permissions are required, or how recurring events are handled. The only behavioral detail available (attendee notification) comes from the schema, not the description.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but for a destructive operation it is arguably too terse rather than efficiently concise. Brevity here looks like under-specification rather than disciplined editing.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive mutation tool with no annotations and no output schema needs the description to explain irreversibility, scope of deletion (especially for recurring events), and side effects. None of these are present, leaving the definition materially incomplete for the operation's risk level.

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 description coverage is 100%, so all three parameters (event_id, calendar_id, notify_attendees) are already documented, including the default for notification. The description adds no meaning beyond the schema, which is acceptable at the baseline.

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?

States a specific verb and resource (delete a calendar event) scoped to Infomaniak, which clearly separates it from the list/get/create/update siblings implied by the names. It stops short of explicitly naming those siblings or describing the delete semantics (single vs. recurring occurrence).

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus calendar_update_event or calendar_get_event, no prerequisites, and no warning about the operation being irreversible. The agent must infer all usage context from the name alone.

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