tickadoo-mcp

list_cities

Read-onlyIdempotent

Use this when the user wants to browse supported cities before searching. Returns city names, slugs, country codes, and product counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of cities to return (1-50). Defaults to 50 when omitted.
`format`	No	Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.	json
`country`	No	Optional country code or country name filter.
`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
`cities`	No
`detail`	No
`message`	No
`error_type`	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": {
+    "cities": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "country": {
+            "type": "string"
+          },
+          "country_code": {
+            "type": "string"
+          },
+          "product_count": {
+            "type": "integer"
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedJun 2, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum number of cities to return (1-50). Defaults to 50 when omitted.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

Changed10 schema fields changedApr 26, 2026

removedInput schema / $schema

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

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

addedInput schema / properties / country

Added value: +{
+  "description": "Optional country code or country name filter.",
+  "type": "string"
+}

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."

removedInput schema / properties / limit

Removed value: -{
-  "default": 50,
-  "description": "Maximum number of cities to return (default 50)",
-  "type": "number"
-}

removedInput schema / properties / query

Removed value: -{
-  "description": "Optional city name or slug filter (e.g. 'new', 'paris', 'tokyo')",
-  "type": "string"
-}

First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context by noting the tool returns product counts and is a browsing/pre-search operation, but it does not disclose details like default limit, ordering, or localization behavior beyond what the schema and output schema already imply.

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 a single, front-loaded sentence that immediately states when to use the tool and what it returns. Every phrase earns its place, with no filler or redundant restating of the tool name.

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 simple, read-only list tool with four fully documented optional parameters and an output schema, the description provides the necessary trigger context and return summary. There are no hidden side effects, required permissions, or complex usage prerequisites to disclose.

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%, and each parameter has its own description, so the baseline is 3. The tool description itself mentions the output fields but adds no extra parameter semantics; the schema handles that burden.

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 clear verb ('browse') and resource ('supported cities') and explicitly positions the tool as a pre-search step, distinguishing it from the many search and recommendation siblings. It also names the return payload (city names, slugs, country codes, product counts), making its 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit context for when to use the tool ('when the user wants to browse supported cities before searching'). It doesn't name specific alternative tools or give exclusion criteria, but the phrase 'before searching' adequately guides selection relative to the sibling search tools.

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.