tickadoo Experiences and Events

get_availability

Read-only

Use this when the user is ready to check live bookable dates, times, prices, or remaining spaces for one selected product. This is the live supplier-check tool; pass product_id from search or slug plus city_slug. Slot price.amount is in MINOR currency units (pence/cents): amount 13125 with currency_code GBP means GBP 131.25. Slot time is venue-local; when the venue timezone is known, timezone carries its IANA name and datetime/next_available carry the real UTC offset (e.g. 2026-07-18T19:30:00+02:00), so they are safe for time math.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_availability"
  }
}

Input Schema

Name	Required	Description
`slug`	No	Product slug. Use with city_slug when product_id is unavailable.
`as_of`	No	Previous ISO timestamp from stale card data; returns a delta when a retained cacheable snapshot changed. Live-only inventory does not retain snapshots and omits this delta.
`fresh`	No	When true, bypasses the 60-second cache and performs a live supplier check, subject to rate limits. Live-only inventory is always checked live regardless of this flag.
`date_to`	No	End date as YYYY-MM-DD or a natural-language phrase (same as date_from). Defaults to 14 days after date_from and is capped to a 365-day window.
`city_slug`	No	City slug required when slug is used.
`date_from`	No	Start date as YYYY-MM-DD, or a natural-language phrase the server resolves: today, tomorrow, this Saturday, next Friday, this weekend, next weekend. Defaults to today.
`party_size`	No	Number of guests. Default 2.
`product_id`	No	Stable product_id from a search or details response. Preferred when available.
`preferred_time`	No	Optional broad time preference such as morning, afternoon, or evening.
`idempotency_key`	No	Optional UUID. Cacheable inventory may reuse an identical response for up to five minutes; live-only inventory always rechecks and never replays a resolved response.

Output Schema

Name	Required	Description	Default
`slug`	No
`slots`	No
`detail`	No
`message`	No
`timezone`	No
`error_type`	No
`product_id`	No
`total_slots`	No
`inventoryLevel`	No
`next_available`	No
`schema_version`	No
`provenance_level`	No
`book_now_confidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 31, 2026

changedInput schema / properties / as_of / description

Previous value: -"Previous ISO timestamp from stale card data; returns delta only when data changed."New value: +"Previous ISO timestamp from stale card data; returns a delta when a retained cacheable snapshot changed. Live-only inventory does not retain snapshots and omits this delta."

changedInput schema / properties / fresh / description

Previous value: -"When true, bypasses the 60-second cache and performs a live supplier check, subject to rate limits."New value: +"When true, bypasses the 60-second cache and performs a live supplier check, subject to rate limits. Live-only inventory is always checked live regardless of this flag."

changedInput schema / properties / idempotency_key / description

Previous value: -"Optional UUID. Reuse for identical responses within five minutes."New value: +"Optional UUID. Cacheable inventory may reuse an identical response for up to five minutes; live-only inventory always rechecks and never replays a resolved response."

Changed4 schema fields changedOct 12, 2026

changedInput schema / properties / date_from / description

Previous value: -"Start date in YYYY-MM-DD. Defaults to today."New value: +"Start date as YYYY-MM-DD, or a natural-language phrase the server resolves: today, tomorrow, this Saturday, next Friday, this weekend, next weekend. Defaults to today."

removedInput schema / properties / date_from / format
```
Removed value: -"date"
```

changedInput schema / properties / date_to / description

Previous value: -"End date in YYYY-MM-DD. Defaults to 14 days after date_from and is capped to a 365-day window."New value: +"End date as YYYY-MM-DD or a natural-language phrase (same as date_from). Defaults to 14 days after date_from and is capped to a 365-day window."

removedInput schema / properties / date_to / format
```
Removed value: -"date"
```

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "book_now_confidence": {
+      "type": "integer"
+    },
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "inventoryLevel": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "next_available": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "product_id": {
+      "type": "string"
+    },
+    "provenance_level": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "slots": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    },
+    "total_slots": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 31, 2026

changedInput schema / properties / date_to / description

Previous value: -"End date in YYYY-MM-DD. Defaults to today plus 14 days and is capped to a 365-day window."New value: +"End date in YYYY-MM-DD. Defaults to 14 days after date_from and is capped to a 365-day window."

Changed1 schema field changedMay 25, 2026

changedInput schema / properties / date_to / description

Previous value: -"End date in YYYY-MM-DD. Defaults to today plus 14 days and is capped to a 90-day window."New value: +"End date in YYYY-MM-DD. Defaults to today plus 14 days and is capped to a 365-day window."

AddedApr 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover read-only safety, but the description adds substantive behavior the agent could not otherwise know: it is a live supplier check, prices are in minor currency units with a worked example, and slot times carry IANA timezone plus real UTC offsets so they are safe for time math. This is exactly the kind of context annotations cannot express.

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?

Three sentences, front-loaded with the when-to-use trigger, then the identifier requirement, then the two data-format caveats. Every sentence carries information an agent needs to interpret the response correctly; nothing is padding.

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 and 100% parameter coverage, the description needn't explain return values, and it still covers currency and timezone interpretation plus caching behavior. The one remaining gap is that it never positions itself against the near-identical check_availability sibling.

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; the description goes beyond the schema by explaining the minor-unit currency convention (13125 GBP = 131.25) and the venue-local timezone/offset semantics, which the schema only gestures at. It also reinforces the product_id-over-slug preference.

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?

States a specific verb and resource: check live bookable dates, times, prices, and remaining spaces for one selected product, and self-identifies as 'the live supplier-check tool'. It does not, however, distinguish itself from the sibling check_availability, leaving ambiguity about which availability tool to pick.

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?

'Use this when the user is ready to check live bookable dates...' gives a clear triggering condition, and it tells the agent which identifiers to pass (product_id from search, or slug plus city_slug). No explicit exclusion or named alternative is given, so the sibling check_availability is never ruled in or out.

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

All tickadoo Experiences and Events 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.

get_availability

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources