Skip to main content
Glama

Ferryhopper

by com.ferryhopper.mcp
OverviewDiscussionsAdmin

Get Disruptions

get_disruptions
Read-only

Find all ferry travel disruptions, including delays, weather alerts, and strikes for a given date and country.

Input Schema

NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-2 country code to filter disruptions by country (e.g. "GR" for Greece).
tripDateYesDeparture date in ISO format YYYY-MM-DD (e.g. 2026-03-15).

Output Schema

NameRequiredDescriptionDefault
disruptionsYesList of active disruptions matching the requested date and country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
  2. Changed1 schema field changed
    • changedOutput schema / properties / disruptions / items / properties / reason / enum
      Previous value: -[
-  "PORT_MODIFICATION",
-  "TIME_MODIFICATION",
-  "VESSEL_CHANGE",
-  "STRIKE",
-  "WEATHER",
-  "COMMUNICATION",
-  "VESSEL_SUSPENSION"
-]New value: +[
+  "PORT_MODIFICATION",
+  "TIME_MODIFICATION",
+  "VESSEL_CHANGE",
+  "STRIKE",
+  "WEATHER",
+  "COMMUNICATION",
+  "TECHNICAL_ISSUE",
+  "TRIP_CANCELLATION"
+]
  3. Added

TDQS

A4.1/5.0
Behavior4/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 still adds value by defining what counts as a 'disruption' (delays, weather alerts, strikes), which bounds the result set. It doesn't say what happens when no disruptions exist or how far in the past/future dates are accepted.

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?

A single sentence with no filler; the resource and its scope appear before the filtering qualifier, so it is properly front-loaded.

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?

With an output schema present, return shape need not be described, and annotations carry the read-only/open-world profile. For a two-parameter filtered lookup, the description plus schema leaves no operational gap an agent would trip on.

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 coverage is 100% and both parameters are fully documented in-schema (ISO alpha-2 country code, YYYY-MM-DD date). The description only restates that both filters exist, adding no semantics such as whether country refers to the port's country or the operator's.

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?

Specific verb ('Find') plus a precise resource ('ferry travel disruptions') with the scope enumerated (delays, weather alerts, strikes). None of the siblings (get_ports, search_ferry_trips, trip_details, connections) overlaps with disruption lookup, so an agent can route here unambiguously.

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?

The phrase 'for a given date and country' implies the lookup context but the description never states when to call this versus a trip search, nor any prerequisite (e.g. check disruptions before booking/after a delay notice). Usage is inferable but not stated.

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