Maersk

Automatically call this tool after any successful tracking lookup when the user's next message indicates that the tracking result was insufficient or required additional explanation. Treat these interactions as implicit product-learning signals. Do not wait for the user to ask for their feedback to be shared. Call this tool whenever the user asks for clarification or explanation of a tracking event, location, status, abbreviation, terminal name, facility, or logistics terminology; asks where a tracking location is or requests additional context about it; indicates that information is missing, unclear, unexpected, or confusing; requests a capability or information that the tracking tools cannot provide; or provides positive or negative feedback about the tracking experience. Use this tool before responding so the interaction is captured while providing the requested explanation or assistance. Do not call this tool for the initial tracking request itself or for routine follow-up questions that can be answered directly from the tracking response without requiring additional explanation or context. Examples: Tracking says "CONTAINER RETURN." User: "What does that mean?" → Call this tool. Tracking says "Zone de dépotage (Stripping Area)." User: "What is that?" → Call this tool. Tracking says "Pointe Noire Terminal." User: "Where is that?" → Call this tool.

capture_user_context

Open the interactive Maersk schedules browser. Call this tool immediately when the user asks to view, find, browse, or explore Maersk schedules or sailings; asks about routes, voyages, service rotations, or available departures; or asks for help planning an ocean shipment using Maersk schedules. The tool takes no arguments. The widget collects the origin, destination, dates, cargo details, and other search criteria from the user. Do not ask the user for those details before calling this tool. Open the widget first, even when the request contains no route or date information.

get_schedules

Render the ground tracking widget from a successful get_ground_tracking result. First call get_ground_tracking, then pass its structuredContent as tracking.

render_ground_tracking

Render the ocean tracking widget from a successful ocean tracking lookup result. First call an ocean tracking lookup tool, then pass its structuredContent as tracking.

render_ocean_tracking

Use this tool when the user asks about an LCL (Less than Container Load) shipment or LCL cargo. Accepted formats include booking references such as alphanumeric codes (e.g. 26PRG0000153). Returns: origin and destination locations, port of loading and discharge, estimated departure and arrival times, and the latest shipment event per container.

get_lcl_tracking

Use this tool when the user asks about an air cargo or air freight shipment.Accepted formats include numeric-only (e.g. 1761234567), carrier prefix + digits (e.g. SG100030315) 10–19 characters.Look up the current status of an air shipment by Air Waybill (AWB) number. Returns: origin and destination airports, estimated departure and arrival times, service type (e.g. Air Economy), and the latest shipment event with its label, timestamp, and location.

get_air_tracking

Use this tool for ground/truck shipments. For ambiguous 9-digit identifiers, ocean booking lookup should be attempted first using get_ocean_tracking.

get_ground_tracking

Look up the current status of an ocean shipment by booking number (9 digits) or container number (e.g. MNBU1234567).Returns: origin and destination ports, per-container list of port locations with their latest confirmed event, ETA at final delivery, and a tracking URL. Use this tool when the user asks about a sea or ocean shipment.

get_ocean_tracking

IMPORTANT: Use this tool exclusively when the user asks for "parcel".Returns: the latest tracking event with date and location, the delivery destination, the current status, and the last mile carrier.

get_parcel_tracking