Skip to main content
Glama
Sign In
Infomaniak Calendar MCP Server

Infomaniak Calendar MCP Server

Official
by Infomaniak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

calendar_list_events

List Infomaniak calendar events within a specified time range, optionally for a chosen calendar, to review scheduled activities.

Instructions

List Infomaniak calendar events within a specified time range

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "calendar_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd time (Date time string)
fromYesStart time (Date time string)
calendar_idNoCalendar ID (optional, uses default if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing operation but does not disclose pagination, ordering, recurring-event handling, authentication requirements, or what the returned events contain.

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?

The description is a single front-loaded sentence with no unnecessary wording. It communicates the core list operation and its time-range constraint efficiently.

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?

With no annotations and no output schema, the description is too sparse to prepare an agent for the response shape or behavioral edge cases. It covers the basic operation but not return values, ordering, pagination, or default-calendar behavior.

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 the input schema already documents from, to, and calendar_id. The description mentions the time range but adds no semantics for date format, timezone handling, or the optional calendar_id behavior beyond what the schema provides.

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 states a specific verb and resource: list Infomaniak calendar events. It also scopes the operation to a specified time range. It does not explicitly distinguish itself from sibling tools such as calendar_get_event, though the list-versus-get distinction is reasonably clear.

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

Usage Guidelines3/5

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

The time-range scope implies usage for retrieving events between two timestamps. However, the description gives no explicit guidance on when to prefer this over calendar_get_event or calendar_list_calendars, and it names no exclusions.

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