Kalender Sync

Search events

search_events

Read-only

Finds events by text across the calendars shared with this access — case-insensitive substring match on title, location and description.

The search only sees what this access may see: it filters the same visibility-rendered data get_availability returns. Calendars limited to free/busy expose no text and therefore can never match — when such calendars are part of this access, a warning says so. "No match" is thus NOT proof that no such event exists.

A match in a calendar the user allowed managing carries event_id, calendar_id, is_organizer and is_recurring — everything update_event, delete_event and respond_to_event need. Act on those directly instead of calling get_availability again for the same appointment.

The range works like get_availability (single span of at most 92 days, lookback bounded to one year). Without from/to the search covers the last 7 days plus the next 85. Cancelled events are not searchable.

Matches include events that do not block time (blocks_time: false) — notably every all-day event from Apple/iCloud. They are ordinary appointments and belong in the answer; do not filter them out when the user asked what is in their calendar.

Check status first: credits_exhausted means this call was NOT performed. Only warnings and credit information are returned in that case; no result data or write confirmation. Tell the user how to restore credits; do not retry automatically.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	End of the range, ISO 8601. Default: 85 days ahead.
`from`	No	Start of the range, ISO 8601. Default: 7 days ago.
`query`	Yes	Text to look for (case-insensitive substring)

Output Schema

TableJSON Schema

Name	Required	Description
`range`	No
`status`	Yes	ok: tool executed; use its result fields. credits_exhausted: not executed; no result fields.
`matches`	No
`sources`	No
`warnings`	No
`resets_at`	No
`truncated`	No
`range_clamped`	No
`credits_required`	No
`credits_available`	No
`unsearchable_calendars`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 11, 2026

addedOutput schema / properties / credits_available
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / credits_required
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / resets_at

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / status

Added value: +{
+  "description": "ok: tool executed; use its result fields. credits_exhausted: not executed; no result fields.",
+  "enum": [
+    "ok",
+    "credits_exhausted"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "range",
-  "range_clamped",
-  "matches",
-  "truncated",
-  "unsearchable_calendars",
-  "sources",
-  "warnings"
-]New value: +[
+  "status"
+]

Changed2 schema fields changedSep 11, 2026

addedOutput schema / properties / matches / items / properties / blocks_time
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / matches / items / required

Previous value: -[
-  "start",
-  "end",
-  "is_all_day",
-  "calendar_id",
-  "calendar_name"
-]New value: +[
+  "start",
+  "end",
+  "is_all_day",
+  "blocks_time",
+  "calendar_id",
+  "calendar_name"
+]

Changed6 schema fields changedSep 10, 2026

addedOutput schema / properties / matches / items / properties / attendees

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "email": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "optional": {
+        "type": "boolean"
+      },
+      "organizer": {
+        "type": "boolean"
+      },
+      "self": {
+        "type": "boolean"
+      },
+      "status": {
+        "enum": [
+          "accepted",
+          "declined",
+          "tentative",
+          "needs_action"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / matches / items / properties / event_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / matches / items / properties / has_other_attendees
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / matches / items / properties / is_organizer
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / matches / items / properties / is_recurring
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / matches / items / properties / more_attendees
```
Added value: +{
+  "type": "number"
+}
```

Changed1 schema field changedAug 26, 2026
- addedOutput schema / properties / sources / items / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```
First observedJul 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses that free/busy-only calendars can never match and emit a warning, that 'no match' is not proof of absence, that cancelled events are unsearchable, and the exact status semantics (credits_exhausted means the call was not performed). This is exceptional 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.

Conciseness4/5

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

Long but well front-loaded and dense with operational content; each paragraph (visibility limits, result fields, range, status) carries distinct and useful information. Slightly verbose for some readers, but nothing is redundant with the schema or annotations.

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

Completeness5/5

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

Given an output schema already defines the return shape, the description covers everything else an agent needs: coverage constraints, default range, and the credit-exhaustion failure mode. Nothing needed to invoke or interpret the call correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: the range behaves like get_availability (single span of at most 92 days, lookback bounded to one year) and defaults to the last 7 days plus the next 85 when from/to are omitted, enriching the schema's brief 'Default: 7 days ago' notes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (finds) and resource (events), and pins down the matching semantics: case-insensitive substring on title, location and description, scoped to calendars shared with this access. An agent can immediately distinguish it from get_availability and the mutation siblings.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use results' event_id/calendar_id to call update_event, delete_event or respond_to_event directly rather than re-calling get_availability. It also instructs not to filter out blocks_time:false events, and tells the agent not to auto-retry on credits_exhausted.

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

All Kalender Sync tools Inspect

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

Need Help?