tickadoo-mcp

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Date to check in YYYY-MM-DD format.
`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

TableJSON 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. Dates show when Glama detected each change.

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 and destructiveHint=false, so the safety profile is covered. The description adds some behavioral context by indicating the tool returns availability, pricing for a party, and a booking link, but does not go deeper into response shape or edge cases. This is sufficient but not richly transparent.

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 two sentences with no filler. The critical usage condition is front-loaded, and the sibling routing appears immediately after, making it very easy for an agent to parse and act on.

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 five-parameter tool with a high-quality schema and an output schema, the description covers the main invocation context, the exact date constraint, the supported question types, and the alternative tool. Nothing essential for selecting or invoking this tool correctly 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 all parameters are documented structurally. The description maps to date and party_size conceptually but adds no new parameter semantics beyond the schema. A baseline of 3 is appropriate when the schema already carries the full definitional load.

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 states a specific verb (check), a clear resource (availability for a specific experience), and a precise scope (exactly one date). It explicitly contrasts itself with get_availability, making its unique role unambiguous.

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 gives explicit conditions for use: user has picked a specific experience and asks about exactly one date. It also names the alternative (get_availability) and the conditions under which that alternative should be chosen, such as browsing a date range or listing upcoming times.

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

All tickadoo-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation2/5

Many tools overlap heavily. search_experiences, search_by_mood, recommend_experiences, search_local_experiences, and find_nearby_experiences all return ranked experience lists with only slightly different input axes. Curated list tools like get_date_night, get_family_day, get_hidden_gems, get_last_minute, get_whats_on_this_week, and whats_on_tonight are also nearly indistinguishable in output shape and purpose, just with different filters. check_availability and get_availability clearly duplicate availability checking

Naming Consistency4/5

The overwhelming majority follow a clear verb_noun pattern (get_experience_details, search_by_mood, list_cities, plan_itinerary). Minor deviations like whats_on_tonight (missing 'get') and check_availability versus get_availability are small inconsistencies but do not cause confusion

Tool Count3/5

23 tools is on the heavy side for an experience-discovery and booking-assistant server. The count is justified by many curated scenarios, but several tools could be consolidated (e.g., all the list-based get_* and whats_on_* tools could be one parameterized tool). It is not excessive enough to be a major problem

Completeness3/5

The domain of discovering and checking availability for experiences is well covered: search, filter by mood/place/natural language, get details, check availability, compare, get related items, and find transportation. However, there are notable gaps: get_travel_tips returns only experience rows despite claiming tips, get_city_guide similarly returns a limited payload, and there is no tool for actual booking/reservation (though the booking link may be external). The legacy check_availability seems redundant

check_availability

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources