Skip to main content
Glama
Sign In

Multi Calendar

by co.lumman
OverviewDiscussionsAdmin

Read an event

events_get
Read-only

Read one event whole, by the account, calendarId and id events_list names: its description as text - cut where one answer cannot carry it all, omittedCharacters counting what was left out, which reads at its web link - every Teams, Zoom or Meet join link found in the event, its place or its words, the organizer and each guest with their role - required, optional or resource - and answer, the first that fit where one answer cannot carry them all, omittedAttendees counting the rest; its kind and privacy as events_list names them, how it shows, the account's own answer, its reminders - the minutes before its start each sounds, or none, which events_edit writes as an empty list, and unsaid where a Google event keeps its calendar's own - and its web link. Times are given as events_list gives them, in the zone named under timeZone, and an occurrence of a recurring series its seriesId and originalStart as events_list names them. An event whose words screen as a prompt attack is withheld. One of Lumman's own busy copies is answered under busyCopy as events_list answers one, saying under about what it is and where it is switched off.

Input Schema

NameRequiredDescriptionDefault
accountYesThe connected account, by the address calendars_list names.
eventIdYesThe event's id, as events_list names it.
providerNoThe account's provider, as calendars_list names it; needed only where two connected accounts share an address.
timeZoneNoAn IANA zone such as Europe/London to answer in; the person's stored one where omitted.
calendarIdNoThe calendar holding the event, by the calendarId events_list names; an event outside the account's default calendar needs it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "google",
-  "microsoft",
-  "icloud"
-]New value: +[
+  "google",
+  "microsoft",
+  "icloud",
+  "caldav"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "google",
-  "microsoft"
-]New value: +[
+  "google",
+  "microsoft",
+  "icloud"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare a safe read-only operation, and the description adds substantial behavior beyond them: prompt-attack screening withholds events, long descriptions are truncated with omittedCharacters, attendee lists are truncated with omittedAttendees, busy copies are returned under busyCopy, and recurring occurrences carry seriesId and originalStart. This is unusually rich behavioral disclosure.

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

Conciseness2/5

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

The description is a single enormous run-on sentence held together by dashes and semicolons, making it difficult to scan. The first clause is front-loaded, but the remainder is structurally poor despite containing useful information.

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?

There is no output schema, so the description must carry the return-value burden, and it does so comprehensively by enumerating event fields, truncation behavior, recurring-instance metadata, reminders, and busy-copy handling. It omits error behavior for missing events or permission failures, which keeps it from a 5.

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 coverage is 100%, so all five parameters are already documented in the schema. The description reinforces that account, calendarId, and eventId follow events_list naming and that timeZone controls the zone of returned times, but it adds no syntax or constraint 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 opening clause gives a specific verb and resource: 'Read one event whole, by the account, calendarId and id.' It clearly reads a single event rather than a list, but the purpose is buried in a long run-on sentence and references to events_list are about naming conventions, not sibling routing.

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?

'Read one event' implies this is the single-event lookup counterpart to events_list, but the description never explicitly says when to use this instead of events_list or other siblings. No prerequisites, exclusions, or error conditions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Multi Calendar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources