Skip to main content
Glama
Sign In
Infomaniak Calendar MCP Server

Infomaniak Calendar MCP Server

Official
by Infomaniak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

calendar_create_event

Schedule a new Infomaniak calendar event by setting title, start and end times, plus optional recurrence, attendees, description, and calendar selection.

Instructions

Create a new 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": {
      "title": "<title>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "calendar_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEvent end time (Date time string)
rruleNoRecurrence rule in RFC 5545 format, e.g. FREQ=WEEKLY;INTERVAL=1;BYDAY=MO or FREQ=DAILY or FREQ=MONTHLY;BYMONTHDAY=15. Use empty string to remove recurrence.
startYesEvent start time (Date time string)
titleYesEvent title
attendeesNoList of attendee email addresses as a JSON array
calendar_idNoCalendar ID (optional, uses default if not provided)
descriptionNoEvent description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare create action. It does not say whether attendees receive invitations, how conflicting or duplicate events are handled, what timezone semantics apply to start/end, or what the call returns on success.

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?

A single front-loaded sentence with zero filler, so it is efficient and immediately scannable. It is terse to the point of under-specification, but nothing in it is wasted.

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?

For a 7-parameter write operation with no annotations and no output schema, the definition is thin: recurrence, attendee notification, default calendar selection and return behavior all go unaddressed. The rich schema partially compensates, but an agent still lacks behavioral context needed to call it confidently.

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%, including a detailed RFC 5545 example for rrule and the default-calendar note for calendar_id, so the schema already does the explanatory work. The description adds no parameter meaning beyond it, which is the expected baseline when coverage is complete.

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?

The description gives a specific verb and resource ("Create a new Infomaniak calendar event"), which cleanly separates it from calendar_get_event, calendar_list_events, calendar_update_event and calendar_delete_event. It stops short of an explicit sibling contrast, but "new" vs. update is unambiguous.

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, no prerequisite or permission notes, and no mention that calendar_id falls back to a default. An agent must infer all usage context from the tool 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