tickadoo-mcp

search_by_mood

Read-onlyIdempotent

Use this when the user describes the feeling or vibe they want rather than a category, such as romantic, relaxing, adventurous, family fun, foodie, luxury, or rainy day. Maps the mood to preset search filters and returns matching experiences.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes	City name or slug, e.g. "london", "new-york", or "paris".
`mood`	Yes	Mood preset. Valid values: adventurous, romantic, relaxing, family_fun, cultural, thrill_seeking, foodie, budget_friendly, luxury, rainy_day.
`limit`	No	Maximum number of experiences to return (1-50). Defaults to the mood preset size 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
`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
`mood`	No
`detail`	No
`message`	No
`results`	No
`error_type`	No
`pagination`	No
`mapped_filters`	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": {
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "mapped_filters": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "mood": {
+      "type": "string"
+    },
+    "pagination": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "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"
+}

Changed1 schema field changedJun 2, 2026

addedInput schema / properties / limit

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

Changed9 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', 'new-york', 'paris', 'tokyo', 'dubai')"New value: +"City name or slug, e.g. \"london\", \"new-york\", or \"paris\"."

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

Previous value: -"Mood preset. Valid values: adventurous, romantic, relaxing, family_fun, cultural, thrill_seeking, foodie, budget_friendly, luxury, rainy_day"New value: +"Mood preset. Valid values: adventurous, romantic, relaxing, family_fun, cultural, thrill_seeking, foodie, budget_friendly, luxury, rainy_day."

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already signal read-only, idempotent, and non-destructive behavior. The description adds useful context beyond the schema by revealing that moods are mapped to preset search filters rather than used as free-text search keywords. This is meaningful behavioral information without contradicting the annotations.

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 tight sentences with the usage trigger front-loaded and the core behavior stated immediately after. Every sentence earns its place, and there is no redundant detail or filler.

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 full parameter schema coverage, an output schema, and read-only annotations, the description provides exactly the missing contextual information: when to invoke the tool and what distinguishes it from category-based search. An agent has everything needed to call it 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 description coverage is 100%, so the schema already documents all parameters clearly. The description adds a few mood examples, but these are also present in the enum. It does not add deeper meaning for city, limit, format, or language beyond the structural schema, so the baseline score of 3 is appropriate.

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 clearly states a specific trigger ('when the user describes the feeling or vibe they want') and a specific behavior ('Maps the mood to preset search filters and returns matching experiences'). It distinguishes itself from category-based search, which separates it from sibling tools like search_experiences.

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 explicitly says when to use the tool: when the user describes a feeling or vibe rather than a category. The examples help an agent identify the right call, but it does not explicitly name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.