Skip to main content
Glama

tickadoo-mcp

by io.github.tickadoo

get_transfer_info

Read-onlyIdempotent

Use this when the user is arriving in a supported city and needs transfer guidance from an airport, station, or port to a hotel coordinate. Returns taxi, metro, bus, and train estimates with durations, costs, and directions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesSupported city: London, Paris, New York, Amsterdam, Barcelona, Rome, or Tokyo.
formatNoResponse shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.json
languageNoBCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
from_typeYesArrival hub type.
to_latitudeYesHotel latitude.
to_longitudeYesHotel longitude.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
detailNo
messageNo
optionsNo
from_typeNo
error_typeNo
distance_kmNo
origin_nameNo
schema_versionNo
hotel_coordinatesNo
origin_coordinatesNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "city": {
+      "type": "string"
+    },
+    "detail": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "distance_km": {
+      "type": "number"
+    },
+    "error_type": {
+      "type": "string"
+    },
+    "from_type": {
+      "type": "string"
+    },
+    "hotel_coordinates": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "options": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "origin_coordinates": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "origin_name": {
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed13 schema fields changed
    • 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: -"Supported city, such as London, Paris, New York, Amsterdam, Barcelona, Rome, or Tokyo."New value: +"Supported city: London, Paris, New York, Amsterdam, Barcelona, Rome, or Tokyo."
    • 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"
+]
    • changedInput schema / properties / from_type / description
      Previous value: -"Arrival hub type: airport, station, or port."New value: +"Arrival hub type."
    • 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."
    • addedInput schema / properties / to_latitude / maximum
      Added value: +90
    • addedInput schema / properties / to_latitude / minimum
      Added value: +-90
    • addedInput schema / properties / to_longitude / maximum
      Added value: +180
    • addedInput schema / properties / to_longitude / minimum
      Added value: +-180
  3. First observed

TDQS

A4.3/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, covering safety. The description adds the behavioral outcome (returns estimates with durations, costs, and directions), which goes beyond annotations and provides useful context for what the agent can expect.

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 sentences with no filler. The first sentence front-loads the usage trigger, and the second lists the return content. Every word earns its place, and it is compact enough to parse quickly.

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?

Given the presence of a full output schema, complete parameter descriptions, and safety-related annotations, the description covers the essential trigger, input context, and return content. No critical information needed to invoke the tool correctly 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 100%, as every parameter (city, format, language, from_type, to_latitude, to_longitude) already has a clear description. The tool description itself adds no additional parameter-level meaning, so the baseline of 3 applies since the schema carries the full 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 uses a specific verb('use'), resource ('transfer guidance'), and scope ('airport, station, or port to a hotel coordinate'), clearly distinguishing it from sibling tools that focus on experiences or city guides. It also names the output content ('taxi, metro, bus, and train estimates'), making the tool's purpose unmistakable.

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 explicitly states when to use the tool: 'when the user is arriving in a supported city and needs transfer guidance.' It does not mention when-not-to-use or name an alternative sibling, but there is no overlapping sibling tool, so the clear trigger context is sufficient 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 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.

TDQS

A3.9/5.0
Disambiguation2/5

Many tools return the same ranked search-row shape for overlapping discovery intents: get_city_guide, get_date_night, get_family_day, get_hidden_gems, get_last_minute, get_whats_on_this_week, plan_itinerary, recommend_experiences, search_by_mood, and whats_on_tonight all blur together despite detailed trigger descriptions. check_availability vs get_availability adds further ambiguity. A few utilities like list_cities, get_transfer_info, and report_quality_signal are clearly distinct, but the experience-list cluster creates real misselection risk.

Naming Consistency5/5

Names follow a consistent snake_case verb_object pattern: get_*, search_*, list_cities, plan_itinerary, render_experience_cards, report_quality_signal, compare_experiences, check_availability. There is no camelCase or mixed verb-style chaos, and even the phrase-based whats_on_tonight fits the readable imperative style.

Tool Count3/5

23 tools is on the heavy side for a discovery-oriented server. Many get_* tools are ranking variants of the same underlying search-results operation and could plausibly be consolidated, even though each has a narrow trigger scenario.

Completeness4/5

The core discovery flow is well covered: search by city, place, mood, or natural language; get details; check availability; compare; find related; render; give feedback; and get transfer info. Some promised features like get_travel_tips and get_city_guide return only search rows rather than real content, and booking is externalized via links, but there are no major dead ends in the main agent workflow.

Resources