Skip to main content
Glama

Ferryhopper

by com.ferryhopper.mcp
OverviewDiscussionsAdmin

Search Trips (Deprecated)

search_trips
Read-only

Deprecated: prefer search_ferry_trips, which covers this tool plus round-trip and multi-leg search and per-segment availability flags. Get a list of available one-way ferry trips between two ports on a specific date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDeparture date in ISO format YYYY-MM-DD (e.g. 2026-03-15).
arrivalLocationYesArrival location as a human-readable name or search term (e.g. city, port name), not a port code.
departureLocationYesDeparture location as a human-readable name or search term (e.g. city, port name), not a port code.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundDirectItinerariesForTripYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / marketingCompany / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / marketingCompany / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "iconURL": {
+        "format": "uri",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "iconURL"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / marketingCompany / properties
      Removed value: -{
-  "iconURL": {
-    "format": "uri",
-    "type": "string"
-  },
-  "name": {
-    "type": "string"
-  }
-}
    • removedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / marketingCompany / required
      Removed value: -[
-  "name",
-  "iconURL"
-]
    • removedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / marketingCompany / type
      Removed value: -"object"
    • changedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / ownerCompany / description
      Previous value: -"This is the original owner of the vessel. This company's code is the one that should be used in the proceeding booking flow."New value: +"This is the original owner of the vessel."
    • changedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / required
      Previous value: -[
-  "vehicleIsMandatory",
-  "departurePort",
-  "arrivalPort",
-  "departureDateTime",
-  "arrivalDateTime",
-  "ownerCompany",
-  "marketingCompany",
-  "vessel",
-  "accommodations"
-]New value: +[
+  "vehicleIsMandatory",
+  "departurePort",
+  "arrivalPort",
+  "departureDateTime",
+  "arrivalDateTime",
+  "ownerCompany",
+  "vessel",
+  "marketingCompany",
+  "accommodations"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / properties / vehicleIsMandatory
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / properties / foundDirectItinerariesForTrip / items / properties / segments / items / required
      Previous value: -[
-  "departurePort",
-  "arrivalPort",
-  "departureDateTime",
-  "arrivalDateTime",
-  "ownerCompany",
-  "marketingCompany",
-  "vessel",
-  "accommodations"
-]New value: +[
+  "vehicleIsMandatory",
+  "departurePort",
+  "arrivalPort",
+  "departureDateTime",
+  "arrivalDateTime",
+  "ownerCompany",
+  "marketingCompany",
+  "vessel",
+  "accommodations"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "foundDirectItinerariesForTrip": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "deepLink": {
+            "description": "A redirection URL to the search results page for the user to proceed to the booking flow",
+            "format": "uri",
+            "type": "string"
+          },
+          "hasETicket": {
+            "description": "Whether e-ticket/mobile boarding is available for this trip.",
+            "type": "boolean"
+          },
+          "hasPets": {
+            "description": "Whether pets are allowed on this trip. True if petPolicy.type is NOTICKET or TICKET.",
+            "type": "boolean"
+          },
+          "hasVehicles": {
+            "description": "Whether vehicle options are available for this trip.",
+            "type": "boolean"
+          },
+          "segments": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "accommodations": {
+                  "description": "Each segment has a list of available accommodations. The accommodation selection will be common for all passengers.",
+                  "items": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "expectedPrice": {
+                        "additionalProperties": false,
+                        "properties": {
+                          "totalPriceInCents": {
+                            "type": "number"
+                          }
+                        },
+                        "required": [
+                          "totalPriceInCents"
+                        ],
+                        "type": "object"
+                      },
+                      "type": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "type",
+                      "expectedPrice"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "arrivalDateTime": {
+                  "description": "Date time is in local time of port. Date time format is 2023-11-29T11:25:00+02:00, including the difference with UTC time",
+                  "format": "date-time",
+                  "type": "string"
+                },
+                "arrivalPort": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name"
+                  ],
+                  "type": "object"
+                },
+                "departureDateTime": {
+                  "description": "Date time is in local time of port. Date time format is 2023-11-29T11:25:00+02:00, including the difference with UTC time",
+                  "format": "date-time",
+                  "type": "string"
+                },
+                "departurePort": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name"
+                  ],
+                  "type": "object"
+                },
+                "marketingCompany": {
+                  "additionalProperties": false,
+                  "description": "Marketing company is the one managing this trip segment. This company and its logo should be used in UI and client side information and displays.",
+                  "properties": {
+                    "iconURL": {
+                      "format": "uri",
+                      "type": "string"
+                    },
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name",
+                    "iconURL"
+                  ],
+                  "type": "object"
+                },
+                "ownerCompany": {
+                  "additionalProperties": false,
+                  "description": "This is the original owner of the vessel. This company's code is the one that should be used in the proceeding booking flow.",
+                  "properties": {
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name"
+                  ],
+                  "type": "object"
+                },
+                "vessel": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name"
+                  ],
+                  "type": "object"
+                }
+              },
+              "required": [
+                "departurePort",
+                "arrivalPort",
+                "departureDateTime",
+                "arrivalDateTime",
+                "ownerCompany",
+                "marketingCompany",
+                "vessel",
+                "accommodations"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "segments",
+          "hasVehicles",
+          "hasPets",
+          "hasETicket",
+          "deepLink"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "foundDirectItinerariesForTrip"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, openWorldHint=true, destructiveHint=false) cover the safety profile. The description adds the deprecation status and the one-way scope, but doesn't disclose other behavioral details like pagination or result ordering. Since annotations already convey safety, a 3 is appropriate for the moderate added context.

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?

Two concise sentences. The deprecation notice is front-loaded, immediately guiding the agent away from this tool, followed by a crisp purpose statement. No redundant or filler content.

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 output schema exists, return values are covered elsewhere. The description explains the deprecation, the alternative, and the exact scope. All required parameters are documented in the schema. An agent has everything needed to decide whether to use this tool and how 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 each parameter (date, arrivalLocation, departureLocation) with clear descriptions. The tool description adds no additional parameter information beyond what's in the schema, so baseline 3 applies.

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?

States the exact function: list one-way ferry trips between two ports on a date. Explicitly names the replacement tool (search_ferry_trips) and the additional features it provides, clearly distinguishing it from siblings. The verb 'Get a list' is specific and the resource is defined.

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?

Explicitly instructs to prefer search_ferry_trips and explains why (covers this tool plus round-trip, multi-leg, per-segment flags). This gives clear when-to-use guidance and names the alternative. The scope is unambiguous: one-way trips on a specific date between two ports.

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

All Ferryhopper toolsInspect
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.

Resources