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.

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	Default
`range`	Yes
`matches`	Yes
`sources`	Yes
`warnings`	Yes
`truncated`	Yes
`range_clamped`	Yes
`unsearchable_calendars`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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?

Annotations cover only the safety profile (readOnly, non-destructive, closed-world). The description goes far beyond: visibility-rendered scope, the warning emitted for free/busy-only calendars, which fields are returned for manageable calendars, the 92-day span and one-year lookback caps, default range, exclusion of cancelled events, and the instruction not to filter blocks_time:false/all-day events.

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?

Purpose is front-loaded in the first sentence, and every subsequent sentence carries non-redundant behavior (visibility, warnings, returned fields, range caps, blocks_time caveat). It is on the long side, but little of it is filler.

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?

For a search tool with an output schema, annotations, and a small parameter set, the description covers everything needed to invoke it correctly and interpret results: scope, limits, defaults, warnings, and the caveat about false negatives.

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 the baseline is 3, but the description adds real meaning beyond the schema: the range behaves like get_availability with a single span capped at 92 days and a one-year lookback bound, and it confirms the from/to defaults. It does not add anything for the required query parameter beyond what the schema states.

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 and resource ('finds events by text') plus the exact matching semantics (case-insensitive substring over title, location, description). It also scopes itself against the sibling get_availability, so an agent can distinguish it without opening either schema.

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?

Explicit routing: use this to find events by text, then act on the returned event_id/calendar_id directly 'instead of calling get_availability again.' It also states the key false-negative condition ('No match is thus NOT proof that no such event exists') and the free/busy visibility limitation.

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?