gcal

get_next_availability

Read-only

Find next 10 available time slots in a calendar. Searches up to 30 days ahead. Returns {availableSlots: [{start, end}...], searchedUntil} with times in the specified timezone. Use searchedUntil with new startFromDate/Time to paginate. Can restrict to specific hours/days. Slots align to startTimeIncrement boundaries.

Input Schema

TableJSON Schema

Name	Required	Description
`duration`	Yes	Duration of the meeting in minutes (e.g., 30, 60, 90)
`timezone`	Yes	Time zone for all operations (IANA format, e.g., "America/New_York")
`calendarId`	Yes	Calendar ID from list_calendars
`includeDays`	No	Days of the week to include in search (default: weekdays only)
`startFromDate`	Yes	Start searching from this date in YYYY-MM-DD format (e.g., "2024-01-15")
`startFromTime`	Yes	Start searching from this time in HH:MM:SS format (e.g., "09:00:00")
`searchHoursEnd`	No	Daily search window end time in HH:MM:SS format (e.g., "17:00:00"). If not provided, searches all hours
`searchHoursStart`	No	Daily search window start time in HH:MM:SS format (e.g., "09:00:00"). If not provided, searches all hours
`startTimeIncrement`	No	Increment between possible start times in minutes (e.g., 15 for every 15 minutes, 30 for every half-hour)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`searchedUntil`	Yes
`availableSlots`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedApr 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / availableSlots / items / properties / end / $ref
```
Removed value: -"#/properties/availableSlots/items/properties/start"
```
- addedOutput schema / properties / availableSlots / items / properties / end / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / availableSlots / items / properties / end / properties
```
Added value: +{
+  "date": {
+    "type": "string"
+  },
+  "dayOfWeek": {
+    "type": "string"
+  },
+  "time": {
+    "type": "string"
+  },
+  "timezone": {
+    "type": "string"
+  }
+}
```
- addedOutput schema / properties / availableSlots / items / properties / end / required
```
Added value: +[
+  "date",
+  "dayOfWeek"
+]
```
- addedOutput schema / properties / availableSlots / items / properties / end / type
```
Added value: +"object"
```

Changed1 schema field changedFeb 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "availableSlots": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "end": {
+            "$ref": "#/properties/availableSlots/items/properties/start"
+          },
+          "start": {
+            "additionalProperties": false,
+            "properties": {
+              "date": {
+                "type": "string"
+              },
+              "dayOfWeek": {
+                "type": "string"
+              },
+              "time": {
+                "type": "string"
+              },
+              "timezone": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "date",
+              "dayOfWeek"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "searchedUntil": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "availableSlots",
+    "searchedUntil"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing safety. The description adds valuable behavioral context beyond annotations: the 30-day search limit, pagination mechanism using searchedUntil, slot alignment to startTimeIncrement boundaries, and the ability to restrict to specific hours/days. This significantly enhances understanding of the tool's operational behavior.

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 efficiently structured in four sentences with zero waste: first states core purpose, second defines search scope and output format, third explains pagination, fourth adds filtering and alignment details. Every sentence contributes essential information without redundancy.

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 the tool's moderate complexity (9 parameters, read-only operation), the description is complete: it explains what the tool does, its constraints (30-day limit), output format, pagination mechanism, and key behavioral details. With annotations covering safety and an output schema presumably documenting the return structure, no critical gaps remain.

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?

With 100% schema description coverage, the input schema already documents all 9 parameters thoroughly. The description adds minimal parameter semantics beyond the schema, mentioning timezone specification and startTimeIncrement alignment, but doesn't provide additional syntax or format details. This meets the baseline expectation when schema coverage is complete.

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?

The description clearly states the specific action ('Find next 10 available time slots in a calendar') and resource ('calendar'), distinguishing it from siblings like get_calendar_events (which retrieves existing events) or create_event (which creates events). The verb 'find' with the quantitative '10 available time slots' provides precise scope.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('Find next 10 available time slots') and implies pagination guidance ('Use searchedUntil with new startFromDate/Time to paginate'), but doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools (e.g., get_calendar_events for viewing existing events).

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

All gcal 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.