get_routes_from_country_b2b
ChatGPTGiven a country ISO code, returns available outbound routes from that country, including routeId, origin port code, destination port code, operator and return-route lookup guidance. Use this when port codes are unknown and you need to discover available routes and ports for quoting. For return journeys, do not assume the outbound routeId can be reused in reverse: use returnRouteLookupHint to find the reverse-direction routeId by calling get_routes_from_port with the destination port code from the outbound route, then select the route whose portTo.code matches the original departure port. For international return journeys, you may need to query both countries to obtain both outbound and inbound routes. This is a good starting point when you do not already know the relevant port code. User-facing narration: - Prefer plain language such as "route", "crossing", "direction", or "sailing". - Say "I’m looking up available routes from the departure country" rather than mentioning numeric identifiers. - Avoid mentioning routeId unless debugging, validating payloads, or the user explicitly asks for technical detail. - Treat routeId as an internal implementation field used for quoting, not default customer-facing wording.






