Advocate

Get Business Availability

get_availability

Read-onlyIdempotent

Return available windows from the business's active configured calendar, using its selected timezone, duration, operating hours, and current local or connected-calendar occupancy; supported scheduling providers supply their own slots. Use a returned window to start a booking. Availability can change before confirmation, including when the calendar provider is unavailable. If this business uses an unsupported calendar or booking provider, call get_booking_destination to find its published public booking route.

Input Schema

Name	Required	Description
`slug`	Yes	Business slug identifier
`window_end`	No	Unix seconds (absolute instant; default now + 7 days). See window_start on reading the response's `timezone`.
`window_start`	No	Unix seconds (absolute instant; default now). The business's own timezone is not an input — it is returned as `timezone` in the response. To target a local phrase like "Tuesday afternoon", request a generously wide window and filter the returned slots using that `timezone`.

Output Schema

Name	Required	Description	Default
`slots`	Yes
`source`	Yes
`timezone`	Yes
`generated_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 21, 2026

changedInput schema / properties / window_end / description

Previous value: -"Unix seconds; default now + 7 days"New value: +"Unix seconds (absolute instant; default now + 7 days). See window_start on reading the response's `timezone`."

changedInput schema / properties / window_start / description

Previous value: -"Unix seconds; default now"New value: +"Unix seconds (absolute instant; default now). The business's own timezone is not an input — it is returned as `timezone` in the response. To target a local phrase like \"Tuesday afternoon\", request a generously wide window and filter the returned slots using that `timezone`."

Changed5 schema fields changedJul 16, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / slug / description

Previous value: -"business slug"New value: +"Business slug identifier"

addedInput schema / properties / window_end / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / window_start / maximum
```
Added value: +9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "generated_at": {
+      "type": "number"
+    },
+    "slots": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "capacity": {
+            "type": "number"
+          },
+          "end": {
+            "type": "number"
+          },
+          "start": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "start",
+          "end",
+          "capacity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slots",
+    "source",
+    "timezone",
+    "generated_at"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedJul 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / slug / description

Previous value: -"Business slug identifier"New value: +"business slug"

removedInput schema / properties / window_end / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / window_start / maximum
```
Removed value: -9007199254740991
```

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "generated_at": {
-      "type": "number"
-    },
-    "slots": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "capacity": {
-            "type": "number"
-          },
-          "end": {
-            "type": "number"
-          },
-          "start": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "start",
-          "end",
-          "capacity"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "source": {
-      "type": "string"
-    },
-    "timezone": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "slots",
-    "source",
-    "timezone",
-    "generated_at"
-  ],
-  "type": "object"
-}New value: +null

Changed5 schema fields changedJul 12, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / slug / description

Previous value: -"business slug"New value: +"Business slug identifier"

addedInput schema / properties / window_end / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / window_start / maximum
```
Added value: +9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "generated_at": {
+      "type": "number"
+    },
+    "slots": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "capacity": {
+            "type": "number"
+          },
+          "end": {
+            "type": "number"
+          },
+          "start": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "start",
+          "end",
+          "capacity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slots",
+    "source",
+    "timezone",
+    "generated_at"
+  ],
+  "type": "object"
+}

First observedMay 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent safety, and the description adds genuinely new context: availability can change before confirmation and may be degraded when the calendar provider is unavailable. It also clarifies that the business timezone is returned rather than supplied, which is behavioral information not in the annotations.

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?

The core purpose is front-loaded in the first clause, and the fallback guidance is placed last where it belongs. It is somewhat dense but every sentence carries actionable 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?

With an output schema present, return shape needn't be explained, and the description still covers the key edge cases (unsupported providers, volatile availability). Nothing essential for correct invocation is missing.

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%, so the schema fully documents slug, window_start, and window_end. The description does not add parameter-level syntax or format detail beyond what the schema already provides, so baseline 3 applies.

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 uses a specific verb and resource ('Return available windows from the business's active configured calendar') and enumerates the inputs that shape the result (timezone, duration, operating hours, occupancy). It also distinguishes itself from the fallback sibling by naming get_booking_destination for unsupported providers.

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?

It states the downstream use ('Use a returned window to start a booking') and routes unsupported-provider cases to get_booking_destination. There are no explicit exclusions beyond that, but the context for calling it is clear.

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

All Advocate 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?