tickadoo Experiences and Events

compare_experiences

Read-onlyIdempotent

Use this when the user wants a side-by-side comparison of 2-5 specific products. Pass the slug for each. Returns a comparison table plus per-axis winners (value, rating, popularity, family-fit).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slugs": "<slugs>"
    },
    "name": "compare_experiences"
  }
}

Input Schema

Name	Required	Description	Default
`slugs`	Yes	Product slugs from earlier search or recommend results.
`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

Name	Required	Description	Default
`text`	No
`detail`	No
`winner`	No
`message`	No
`comparison`	No
`error_type`	No
`differences`	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": {
+    "comparison": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "differences": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    },
+    "winner": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

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

Previous value: -"Array of 2-5 tickadoo slugs or booking paths to compare side-by-side."New value: +"Product slugs from earlier search or recommend results."

removedInput schema / properties / slugs / items / minLength
```
Removed value: -1
```

First observedApr 14, 2026

TDQS

A3.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is transparent. However, the description says it 'Returns a comparison table,' while the schema's format parameter states text format returns 'a short narrative paragraph' — so the claimed output shape is not accurate across all supported modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the use case, and no filler. It earns most of its space, but the 'comparison table' wording is slightly imprecise given the text/narrative format option, which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description is mostly complete: it communicates cardinality, required input, and output highlights. The only material gap is the inconsistent return-format claim, which could mislead an agent choosing between json and text.

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 slugs, format, and language. The description only restates the slug requirement and adds no new parameter semantics beyond what the schema provides, so it stays at the baseline 3.

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 names a specific operation — side-by-side comparison — and bounds it to 2-5 specific products. It also previews the output (comparison table plus per-axis winners), which distinguishes it clearly from search, recommendation, and detail-lookup siblings.

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 an explicit trigger: 'Use this when the user wants a side-by-side comparison of 2-5 specific products.' It does not explicitly name alternative tools or state when not to use it, so it misses the full 5, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All tickadoo Experiences and Events 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.