tickadoo Experiences and Events

check_availability

Read-only

Use this when the user has picked a specific experience and asks about exactly one date: whether it is available that day, what it costs for a party, or a booking link for that date. For browsing a date range or listing upcoming times and live slot prices, use get_availability.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "date": "<date>"
    },
    "name": "check_availability"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Date to check as YYYY-MM-DD, or a natural-language phrase the server resolves: today, tomorrow, this Saturday, next Friday, this weekend, next weekend.
`slug`	Yes	Product slug or legacy booking path, e.g. "london-dungeon-tickets" or "/london/london-dungeon-tickets".
`format`	No	Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.	json
`language`	No	BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
`party_size`	No	Number of guests or tickets to price. Default 2.

Output Schema

Name	Required	Description	Default
`date`	No
`slug`	No
`slots`	No
`title`	No
`detail`	No
`message`	No
`available`	No
`error_type`	No
`schema_version`	No
`total_for_party`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

changedInput schema / properties / date / description

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

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

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "date": {
+      "type": "string"
+    },
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "slots": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_for_party": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed13 schema fields changedApr 26, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

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

changedInput schema / properties / date / description

Previous value: -"Date to check in ISO format YYYY-MM-DD (e.g. '2026-04-05')"New value: +"Date to check in YYYY-MM-DD format."

addedInput schema / properties / date / format
```
Added value: +"date"
```
changedInput schema / properties / format / default
```
Previous value: -"text"New value: +"json"
```

changedInput schema / properties / format / description

Previous value: -"Response format: text (default) or json"New value: +"Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces."

changedInput schema / properties / format / enum

Previous value: -[
-  "text",
-  "json"
-]New value: +[
+  "json",
+  "text"
+]

removedInput schema / properties / language / default
```
Removed value: -"en"
```

changedInput schema / properties / language / description

Previous value: -"Supported language code for localised booking URLs (e.g. 'en', 'de', 'fr', 'es', 'ja', 'pt-br')"New value: +"BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted."

changedInput schema / properties / party_size / description

Previous value: -"Number of guests or tickets to price (default 2, max 50)"New value: +"Number of guests or tickets to price. Default 2."

addedInput schema / properties / party_size / maximum
```
Added value: +50
```
addedInput schema / properties / party_size / minimum
```
Added value: +1
```

changedInput schema / properties / slug / description

Previous value: -"Tickadoo slug or booking path, e.g. 'london-dungeon-tickets' or '/london/london-dungeon-tickets'"New value: +"Product slug or legacy booking path, e.g. \"london-dungeon-tickets\" or \"/london/london-dungeon-tickets\"."

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is carried structurally; the description's added value is naming the payable outputs (availability, party cost, booking link) and the single-date scope. It does not explain the unusual idempotentHint=false or the pricing freshness/rate-limit behavior, so it is useful but not rich.

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?

Two sentences, zero filler, with the positive trigger front-loaded and the sibling routing placed after it. Every clause earns its place.

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?

An output schema exists and annotations cover safety, so the description need not explain return values; combined with full schema coverage and explicit sibling routing, an agent has everything required to select and invoke this tool correctly.

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%, including natural-language date resolution, slug formats, format enum, language, and party_size bounds, so the schema does the heavy lifting. The description only gestures at party_size ('what it costs for a party') without adding syntax or semantics beyond the schema; 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 names a precise verb+resource+scope: check one specific experience on exactly one date, returning availability, party pricing, or a booking link. It explicitly contrasts with the sibling get_availability, so an agent can route between them 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?

It states the triggering condition ('user has picked a specific experience and asks about exactly one date') and names the alternative tool plus the condition that selects it (date-range browsing, upcoming times, live slot prices → get_availability). Nothing is left to inference.

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.