Ferryhopper

Get Direct Connections

get_direct_connections_for_ports

Read-only

Find all direct ferry routes and reachable destination ports from a given origin port without layovers or transfers.

Input Schema

Name	Required	Description	Default
`portLocation`	Yes	Location name or search term used to find matching ports (not limited to exact port codes).

Output Schema

Name	Required	Description	Default
`departurePort`	Yes	The name of the departure port
`connectedDestinations`	Yes	List of ports directly connected to the departure port

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedFeb 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "connectedDestinations": {
+      "additionalProperties": false,
+      "description": "List of ports directly connected to the departure port",
+      "properties": {
+        "ports": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "code": {
+                "description": "The unique code of the port",
+                "type": "string"
+              },
+              "countryName": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "countryName",
+              "code"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "ports"
+      ],
+      "type": "object"
+    },
+    "departurePort": {
+      "description": "The name of the departure port",
+      "type": "string"
+    }
+  },
+  "required": [
+    "departurePort",
+    "connectedDestinations"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope by stating results are limited to direct routes with no layovers or transfers, but it does not add other behavioral details such as auth needs, rate limits, or result shape.

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 a single efficient sentence with the core scope front-loaded. Every phrase contributes to clarifying direct routes, destination ports, and the no-transfer constraint.

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?

For a simple read-only lookup with one fully described parameter, rich annotations, and an output schema, the description is largely complete. It clearly states the direct-route constraint, though it could clarify whether multiple matching origin ports are considered.

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%, and the single portLocation parameter is already documented as a location name or search term. The description reinforces that it is the origin port but adds no additional syntax, format, or matching behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: finding direct ferry routes and reachable destination ports from an origin port, explicitly excluding layovers and transfers. It is clear and specific, but it does not name or directly contrast with sibling tools such as search_ferry_trips or search_trips.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'without layovers or transfers,' which signals this tool is for direct connections only. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives for trips involving transfers or disruptions.

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

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

Resources

Need Help?