tickadoo-mcp

get_city_guide

Read-onlyIdempotent

Use this when the user wants an orientation overview of a city for trip planning. Returns a ranked list of the city's most popular bookable experiences (search rows); derive the dominant categories and price levels from those rows rather than expecting a structured guide payload.

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
`language`	No	BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.

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.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "_normalization": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "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": {
+            "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"
+    },
+    "message": {
+      "type": "string"
+    },
+    "pagination": {
+      "additionalProperties": true,
+      "properties": {
+        "limit": {
+          "type": "integer"
+        },
+        "offset": {
+          "type": "integer"
+        },
+        "total": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "request_id": {
+      "type": "string"
+    },
+    "results": {
+      "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"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed8 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 / city / description

Previous value: -"City name or slug (e.g. 'london', 'prague', 'new-york', 'rome')"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."

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already establish this as a safe, read-only, idempotent operation. The description adds valuable behavioral context beyond that: the response is actually a ranked list of search rows, and the agent must derive categories and price levels from those rows rather than expecting a structured guide. This prevents a major misinterpretation of the return payload.

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: the first states the trigger use case, the second states the return shape and the key interpretive instruction. Every sentence earns its place with no redundancy.

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?

The tool is simple, the schema fully documents its parameters, annotations cover safety, and an output schema exists. The description fills the one important gap by explaining how to interpret the returned rows. Nothing essential is missing for correct invocation.

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?

The input schema already describes all three parameters in full, so the schema carries the semantic weight. The description adds no additional parameter-level detail, which is acceptable given the 100% schema coverage.

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 clearly states the tool returns an orientation overview of a city for trip planning: a ranked list of popular bookable experiences. It also clarifies that no structured guide payload should be expected. While it doesn't explicitly name sibling alternatives, the use case and output format are specific enough to set it apart from search and tip tools.

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?

The description opens with an explicit when-to-use condition: 'when the user wants an orientation overview of a city for trip planning.' It doesn't enumerate alternatives or exclusions, so it stops short of full routing guidance, but the context is clear and actionable.

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.