tickadoo-mcp

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.

Input Schema

TableJSON 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 delta only when data changed.
`fresh`	No	When true, bypasses the 60-second cache and performs a live supplier check, subject to rate limits.
`date_to`	No	End date in YYYY-MM-DD. 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 in YYYY-MM-DD. 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. Reuse for identical responses within five minutes.

Output Schema

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

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?

The description goes beyond annotations by explaining that price.amount is in minor currency units and that slot times are venue-local with timezone offsets safe for time math. These are exactly the kind of pitfalls that prevent unit and timezone errors. It aligns with readOnlyHint=true and destructiveHint=false, so no contradiction.

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?

Four sentences, each doing work: purpose, product selection, currency-unit warning, and timezone warning. No filler, and the most important usage guidance is front-loaded.

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 100% schema coverage, output schema, and annotations, the essentials are covered: when to use, what input to supply, and how to interpret money and time. The description is complete enough for an agent to call correctly; remaining details are left to the schema.

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?

All 10 parameters have descriptions in the schema, so the baseline is 3. The description mostly restates the product_id/slug+city_slug selection rule already in the schema and adds little new parameter-level semantics. The price/time details relate to output interpretation rather than parameter meaning.

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?

The description names a specific action ('check live bookable dates, times, prices, or remaining spaces') and a resource ('one selected product'), clearly distinguishing this from broader search/exploration tools. However, a sibling named check_availability exists and the description never explicitly differentiates the two, so it falls short of full sibling differentiation.

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 gives a clear trigger ('Use this when the user is ready to check live bookable...') and a routing rule ('pass product_id from search or slug plus city_slug'). It does not mention when not to use it or name alternatives such as check_availability, so it gets a 4 rather than 5.

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

get_availability

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources