Skip to main content
Glama

tickadoo-mcp

by io.github.tickadoo
OverviewDiscussionsAdmin

render_experience_cards

Read-onlyIdempotent

Use this immediately after ANY discovery or search tool (search_experiences, whats_on_tonight, get_last_minute, get_whats_on_this_week, recommend_experiences, search_by_mood, get_hidden_gems, get_family_day, get_date_night, search_local_experiences) returns results. It is the only tool that displays the visual experience cards, so always call it once for every result set you want shown. Take the experience_ids those tools provide and render them; pass the product_id values exactly as returned by those tools, never full product rows. Only experience_ids and render_type are required. Optionally pass render_context.intent_summary (a short phrase describing what the user asked for, e.g. city, date, audience) to set the carousel heading. Call it exactly once per result set, and do not also re-list the experiences as text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
render_typeYesVisual layout requested for the widget.
experience_idsYesThe stable product_id values from search_experiences results (the product_id field of each returned row). Pass IDs only, never full product rows.
render_contextNo
idempotency_keyNoOptional UUID. Reuse for identical card render responses within five minutes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / oneOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "experience_ids": {
+        "description": "The stable product ids rendered as cards.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "experience_ids"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "detail": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "error_type": {
+        "enum": [
+          "ambiguous_input",
+          "invalid_input",
+          "rate_limited",
+          "supplier_unavailable",
+          "circuit_breaker_open",
+          "partial_result",
+          "unauthorized",
+          "forbidden",
+          "internal_error",
+          "not_found"
+        ],
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retry_after": {
+        "type": "string"
+      },
+      "retry_after_seconds": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "schema_version": {
+        "const": "https://mcp.tickadoo.com/schemas/tool_error/1.0"
+      }
+    },
+    "required": [
+      "schema_version",
+      "error_type",
+      "message",
+      "detail"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties
      Removed value: -{
-  "experience_ids": {
-    "description": "The stable product ids rendered as cards.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "experience_ids"
-]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "experience_ids": {
+      "description": "The stable product ids rendered as cards.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "experience_ids"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "experience_ids",
-  "render_type",
-  "render_context"
-]New value: +[
+  "experience_ids",
+  "render_type"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / experience_ids / description
      Previous value: -"Stable product IDs from search_experiences. Pass IDs only, never full product rows."New value: +"The stable product_id values from search_experiences results (the product_id field of each returned row). Pass IDs only, never full product rows."
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavior beyond annotations: it is the only display tool, pass only product_id values never full rows, call exactly once per result set, and render_context.intent_summary controls the carousel heading. This is useful contextual behavior not captured in annotations.

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?

The description is longer than average, but every sentence carries operational weight: when to call, what to pass, how many times, and what not to do. The enumerated list of sibling tools is a bit bulky but serves a concrete routing purpose. It is front-loaded with the most critical timing instruction.

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 tool with nested parameters and an output schema, the description is complete: it covers timing, prerequisites, ID format, required vs optional fields, call frequency, and the no-text-listing constraint. The render_type enum and return behavior are adequately covered by the schema and output schema, so nothing essential is missing.

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 75%, and most parameter semantics are already in the schema, including the instruction to pass IDs only. The description does add a small clarification that render_context.intent_summary sets the carousel heading and emphasizes passing product_id values exactly as returned, but it largely reinforces schema content rather than providing substantial new parameter meaning.

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 the tool's function: render visual experience cards from discovery/search results. It explicitly names the only rendering tool and distinguishes it from the many search and discovery siblings by saying 'It is the only tool that displays the visual experience cards.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description gives highly explicit when-to-use guidance: call immediately after any listed discovery or search tool returns results, call exactly once per result set, and do not also re-list experiences as text. It names the trigger tools and provides a clear exclusion, leaving no ambiguity about invocation.

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

All tickadoo-mcp toolsInspect
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.

Resources