Skip to main content
Glama
Sign In

Multi Calendar

by co.lumman
OverviewDiscussionsAdmin

Show busy time everywhere

busy_everywhere_set
DestructiveIdempotent

Show one of an account's own calendars as busy in another connected account the person names, or stop: within seconds each busy event of the coming 60 days appears as a private block titled "Busy · <the calendar's account address> (Multi Calendar connector)" - on iCloud, which keeps no private events, or a calendar server, which may keep none, a block titled "Busy (Multi Calendar connector)" - in the main calendar of the account named, while it allows changing events - never in another calendar, and never in an account nobody named, one connected later included - one block per busy time however many calendars named into it hold it. A block moves with its event, goes when the event ends or goes or the pair is taken away, and is placed again if removed by hand; events_list answers blocks apart from events under busyCopies, and no tool counts, moves or cancels one. Naming a pair answers under shows the sentence to give the person word for word. calendars_list names each calendarId and the accounts each calendar already shows busy in.

Input Schema

NameRequiredDescriptionDefault
onYesTrue names the pair, false takes it away.
intoYesThe other connected account to show its busy time in, by the address calendars_list names.
accountYesThe connected account, by the address calendars_list names.
providerNoThe account's provider, as calendars_list names it; needed only where two connected accounts share an address.
calendarIdYesThe calendar, by the calendarId calendars_list names.
intoProviderNoThe account's provider, as calendars_list names it; needed only where two connected accounts share an address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / intoProvider / enum
      Previous value: -[
-  "google",
-  "microsoft",
-  "icloud"
-]New value: +[
+  "google",
+  "microsoft",
+  "icloud",
+  "caldav"
+]
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "google",
-  "microsoft",
-  "icloud"
-]New value: +[
+  "google",
+  "microsoft",
+  "icloud",
+  "caldav"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / intoProvider / enum
      Previous value: -[
-  "google",
-  "microsoft"
-]New value: +[
+  "google",
+  "microsoft",
+  "icloud"
+]
    • 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?

Beyond the annotations, it discloses that blocks appear within seconds for the coming 60 days, are private, move with their events, disappear when events end or the pair is removed, and are recreated if manually deleted. It also explains provider-specific behavior, scope limits, and how events_list exposes blocks under busyCopies.

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 dense, run-on construction with multiple em-dash-separated clauses that make it hard to scan. It is not front-loaded beyond the opening clause and repeats scope constraints in a way that slows comprehension.

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?

For a complex, destructive, idempotent mutation with no output schema, the description covers the important effects, edge cases, and relevant sibling references. It does not describe the immediate return value of this tool, but it explains enough about resulting state and related listings to support correct invocation.

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%, and the schema already explains every parameter, including the provider fields and the boolean on/off switch. The description confirms the conceptual pairing of account, calendarId, and into, but adds little parameter-level syntax or format detail beyond the schema.

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: it shows one of an account's calendars as busy in another named connected account, or stops that pairing. The core action is distinguishable from sibling tools, though the purpose is buried inside a long, clause-heavy sentence.

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?

It explains the toggle behavior and the effect of naming a pair, and it points to calendars_list for account/calendar identifiers. However, it does not explicitly state when to use this tool versus alternatives or give clear prerequisites beyond the schema.

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