Skip to main content
Glama

ocean-schedules

by io.github.lxxmng
OverviewDiscussionsAdmin

find_best_sailings

Decision query: the best upcoming sailings on a lane, ONE per carrier (next bookable departure), ranked. Filter by date window, max transit days, min on-time reliability, cut-off still open, and direct-vs-transshipment. Use this to answer "what should I book?". etd, eta, cutoff.at and the from/to window are port-local times with no timezone offset (2026-10-01T13:00:00): quote the digits, do not convert; only retrieved_at is UTC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest departure date YYYY-MM-DD (default: +60 days)
fromNoEarliest departure date YYYY-MM-DD (default: today)
sortNoRanking (default recommended = reliability blended with transit)
cutoffNoOnly sailings whose booking cut-off has not passed. Sailings where no cut-off is held are kept by default; each option carries cutoff_status saying which case it is.
originYesOrigin port UN/LOCODE or name resolves upstream, e.g. CNSHA
destinationYesDestination port UN/LOCODE, e.g. NLRTM
transshipmentNotrue keeps only sailings that change ship, false only sailings proven direct. Omit it for both: a sailing whose routing we do not hold is returned by neither side, because we will not call a sailing direct without evidence.
max_transit_daysNoMaximum transit time in days
reliability_floorNoMinimum 90-day on-time %, 0-100
cutoff_include_unknownNoDefault true. false narrows to sailings where a deadline is actually held and still ahead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cutoff
      Added value: +{
+  "const": "open",
+  "description": "Only sailings whose booking cut-off has not passed. Sailings where no cut-off is held are kept by default; each option carries cutoff_status saying which case it is.",
+  "type": "string"
+}
    • addedInput schema / properties / cutoff_include_unknown
      Added value: +{
+  "description": "Default true. false narrows to sailings where a deadline is actually held and still ahead.",
+  "type": "boolean"
+}
    • removedInput schema / properties / cutoff_open
      Removed value: -{
-  "description": "Only sailings whose booking cut-off has not passed",
-  "type": "boolean"
-}
    • removedInput schema / properties / direct_only
      Removed value: -{
-  "description": "Exclude transshipment routings",
-  "type": "boolean"
-}
    • addedInput schema / properties / transshipment
      Added value: +{
+  "description": "true keeps only sailings that change ship, false only sailings proven direct. Omit it for both: a sailing whose routing we do not hold is returned by neither side, because we will not call a sailing direct without evidence.",
+  "type": "boolean"
+}
  2. First observed

TDQS

Score is being calculated.

All ocean-schedules 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