Skip to main content
Glama

compare_modes

Compare ocean, air, and sea-air transport modes based on total economic cost, including capital, holding, and stockout costs, to recommend the most cost-effective option for your shipment.

Instructions

Decide the TRANSPORT MODE for a shipment — OCEAN vs AIR vs SEA-AIR — on TOTAL economic cost, not just freight. The other tools price the ocean move; this one answers the importer's prior question: should these goods even go by sea? It costs all three modes and recommends the economically optimal one. Air is priced correctly on the IATA CHARGEABLE WEIGHT = max(actual gross weight, volumetric weight at 167 kg/m³) with an air fuel (FSC) + security (SSC) + handling stack — so bulky-but-light cargo is properly penalised (the lever a naïve 'air is just faster' estimate misses). Sea-air is modeled via the real hubs (Asia→Europe via Dubai/Jebel Ali, Asia→US-East via a US-West gateway): a cheap ocean leg to the hub + a short air final leg. The recommendation runs a real DECISION MODEL: cost of CAPITAL tied up in transit (value × annual rate × days), a p90 safety-stock HOLDING cost from each mode's variability, and — if you pass a deadline — an EXPECTED STOCKOUT cost from the probability the mode arrives late. So for high-value goods (or a tight deadline) air/sea-air can win even though the freight is far dearer, while for cheap goods ocean's much lower freight dominates. Returns the full ocean/air/sea-air table (freight, p50/p90 transit, capital, holding, stockout, total economic cost) + the recommended mode + the trade-off math. Every figure is modeled and tagged; air rates are volatile so they are honest BANDS, not a quote. PREMIUM: pay per call with x402 (USDC on Base) or set a prepaid key (FREIGHT_PULSE_KEY). Same UN/LOCODE port normalization as get_spot_rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port (city name, UN/LOCODE, or 'City, Country'). Same resolution as get_spot_rate.
dest_portYesDestination port (city name, UN/LOCODE, or 'City, Country').
container_typeNoContainer size '20ft'/'40ft'/'40HC' for the ocean leg. Optional; defaults to '40ft'.
valueYesMerchandise value in USD — REQUIRED. It is the capital tied up in transit and the basis of the whole mode trade-off.
weight_kgNoShipment gross weight in kg. Provide this and/or volume_m3 — air is billed on the chargeable weight (max of actual and volumetric).
volume_m3NoShipment volume in cubic metres. Drives the IATA volumetric weight (m³ × 167 kg). Provide this and/or weight_kg.
deadlineNoOptional hard arrival deadline (ISO 'YYYY-MM-DD'). If given, the engine adds an expected-stockout cost from each mode's probability of arriving late.
stockout_penaltyNoUSD penalty if the goods miss the deadline (lost sale / line-down / expedite). Defaults to the goods' value when a deadline is given without one. Optional.
annual_capital_rate_pctNoAnnual cost-of-capital as a fraction (e.g. 0.12 = 12%/yr) for goods in transit. Optional; default 0.12.
annual_holding_rate_pctNoAnnual inventory holding/carrying rate as a fraction (e.g. 0.25 = 25%/yr) for the p90 safety-stock buffer. Optional; default 0.25.
bandNoAir/sea-air rate band to use: 'low', 'typical' or 'high'. Optional; default 'typical'.
jet_fuel_proxyNoOptional jet-fuel proxy to drive the air FSC. Omit for a modeled reference level.
ship_dateNoIntended ship date (ISO). Drives the ocean seasonal surcharges & transit window. Optional; defaults to today.
estimated_days_at_portNoDays the box dwells at destination (adds D&D to the ocean freight leg). Optional.
free_daysNoCarrier free days before D&D on the ocean leg (default 5 if a dwell is given). Optional.
overweightNoFlag an overweight ocean load (freight surcharge). Optional.
fuel_proxyNoOptional VLSFO $/tonne for the ocean BAF model. Optional.
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses the cost model (capital, holding, stockout), IATA chargeable weight calculation, sea-air hub routing, and that air rates are bands. It also mentions premium payment via x402 or prepaid key.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat lengthy but well-structured: purpose first, model details, return format, payment info. Every sentence adds value, though some detail could be streamlined. It is front-loaded with the primary decision.

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?

Given 17 parameters and no output schema, the description thoroughly explains the return value (table with freight, transit times, cost components, recommendation) and the decision model. It covers all necessary context for an agent to understand when and how to invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions already provide 100% coverage with clear explanations of each parameter. The tool description adds context on how parameters like 'value' and 'deadline' drive the trade-off, but the main value comes from the schema descriptions themselves.

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?

The description clearly states the tool decides the transport mode (OCEAN vs AIR vs SEA-AIR) based on total economic cost, distinguishing it from sibling tools that price the ocean move. It uses specific verbs ('Decide the TRANSPORT MODE') and identifies the resource ('shipment').

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool ('answers the importer's prior question: should these goods even go by sea?') and contrasts with alternatives ('The other tools price the ocean move'). Provides context for when air/sea-air wins over ocean based on value and deadlines.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/freight-pulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server