tickadoo-mcp

whats_on_tonight

Read-only

Use this when the user asks what is on in a city tonight. Returns evening-appropriate experiences currently on sale, with out-of-season products filtered out, evening-led options ranked first, and multi-day passes, travel cards and transport products ranked last. Top results carry start_time (venue-local) when the live supplier calendar confirms a performance in the evening window (late afternoon onward); a confirmed slot lifts a row, and timed rows sort soonest-first within one relevance band. Rows without start_time have no confirmed evening time. Confirm the selected experience with get_availability before stating it is bookable tonight.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes	City slug.
`format`	No	Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.	json
`category`	No	Optional category slug to narrow results.
`language`	No	BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
`max_results`	No	Default 10, max 30.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`detail`	No
`message`	No
`results`	No
`error_type`	No
`pagination`	No
`request_id`	No
`experiences`	No
`_normalization`	No
`schema_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedSep 3, 2026

addedOutput schema / properties / _normalization

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / error_type
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / experiences

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "booking_url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "category": {
+        "type": "string"
+      },
+      "city": {
+        "type": "string"
+      },
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "image_url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "additionalProperties": true,
+        "properties": {
+          "amount_minor": {
+            "type": "integer"
+          },
+          "currency": {
+            "type": "string"
+          },
+          "display": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "product_id": {
+        "description": "Stable experience identifier for detail, availability, related-experience, and card-rendering calls.",
+        "type": "string"
+      },
+      "rating": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "review_count": {
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "slug": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "venue": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "product_id",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / pagination / properties / offset
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / request_id
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / results / description
```
Removed value: -"Ranked bookable experiences."
```
removedOutput schema / properties / results / items / properties / name / description
```
Removed value: -"Display name of the experience."
```

changedOutput schema / properties / results / items / properties / product_id / description

Previous value: -"Stable identifier for this experience. Pass these values into render_experience_cards (experience_ids) to show the results as visual cards."New value: +"Stable experience identifier for detail, availability, related-experience, and card-rendering calls."

addedOutput schema / properties / results / items / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / venue
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / schema_version
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJun 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "pagination": {
+      "additionalProperties": true,
+      "properties": {
+        "limit": {
+          "type": "integer"
+        },
+        "total": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "results": {
+      "description": "Ranked bookable experiences.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "booking_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category": {
+            "type": "string"
+          },
+          "city": {
+            "type": "string"
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "image_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Display name of the experience.",
+            "type": "string"
+          },
+          "price": {
+            "additionalProperties": true,
+            "properties": {
+              "amount_minor": {
+                "type": "integer"
+              },
+              "currency": {
+                "type": "string"
+              },
+              "display": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "product_id": {
+            "description": "Stable identifier for this experience. Pass these values into render_experience_cards (experience_ids) to show the results as visual cards.",
+            "type": "string"
+          },
+          "rating": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "review_count": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "product_id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed14 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 / category / description

Previous value: -"Optional category filter. Valid values: theatre, musicals, tours, food, family, nightlife, sightseeing, concerts, comedy, shows, outdoor, workshops, cruises, sports."New value: +"Optional category slug to narrow results."

removedInput schema / properties / category / enum

Removed value: -[
-  "theatre",
-  "musicals",
-  "tours",
-  "food",
-  "family",
-  "nightlife",
-  "sightseeing",
-  "concerts",
-  "comedy",
-  "shows",
-  "outdoor",
-  "workshops",
-  "cruises",
-  "sports"
-]

changedInput schema / properties / city / description

Previous value: -"City name or slug (e.g. 'london', 'new-york', 'paris', 'tokyo', 'dubai')"New value: +"City slug."

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 / max_results / description

Previous value: -"Maximum number of experiences to return (default 10, max 25)"New value: +"Default 10, max 30."

addedInput schema / properties / max_results / maximum
```
Added value: +30
```
addedInput schema / properties / max_results / minimum
```
Added value: +1
```
changedInput schema / properties / max_results / type
```
Previous value: -"number"New value: +"integer"
```

First observedApr 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description richly discloses behavior beyond the annotations: out-of-season filtering, evening-led ranking, multi-day passes/transport ranked last, start_time presence meaning a confirmed live-supplier evening slot, and the sort semantics within a relevance band. It also explains what missing start_time means, which is critical for correct interpretation.

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?

Every sentence earns its place: the trigger, the ranking behavior, the start_time semantics, and the required confirmation step. The description is dense but not bloated, and the most important usage condition 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?

With an output schema present, return structure is covered externally. The description supplies the query intent, ranking/filtering rules, a caveat about unconfirmed times, and a mandatory next step. An agent has enough information 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 coverage is 100%, so parameter meaning is already fully documented in the input schema. The description adds context about the tool's overall behavior but does not need to repeat parameter details. This meets the baseline for a fully covered schema.

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?

States a specific verb and resource: returns evening-appropriate experiences for a city tonight. It clearly differentiates from siblings like get_whats_on_this_week by anchoring on 'tonight' and the user's 'what is on' intent. The scope is further sharpened by filtering and ranking constraints.

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?

Opens with an explicit trigger condition: 'Use this when the user asks what is on in a city tonight.' It also tells the agent to follow up with get_availability before confirming bookability. It does not enumerate when to prefer sibling tools like get_whats_on_this_week or search_experiences, so it falls just short of a 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.