Skip to main content
Glama

ship_decision

Integrates all freight-pulse layers to produce one actionable decision for a shipment: recommended mode, carrier, timing, total landed cost, and key risks with mitigations, considering urgency and deadlines.

Instructions

The UNIFIED decision tool — integrates EVERY freight-pulse layer (rate/forecast, all-in cost, transit & reliability, mode-choice, procurement, port congestion, carrier/alliance, emissions, equipment availability, Incoterms, demurrage & detention, and cargo insurance) into ONE actionable answer for a CONCRETE shipment. This is the tool that makes freight-pulse insustituible: it doesn't just price one layer, it WEIGHS them all coherently. Give the lane + merchandise value (+ optional weight/volume, ship date, urgency, deadline, product, Incoterm, carrier) and it returns: the recommended MODE (urgency-aware — a critical deadline can override the economic optimum toward air/sea-air), the recommended CARRIER for the corridor, the book-now / book-soon / wait / monitor TIMING (the forecast call, overlaid with a building congestion/equipment crunch), the total COST PUESTO EN DESTINO (landed: goods + freight + duty + import tax, when a product is given), and the KEY RISKS with concrete MITIGATIONS (Red-Sea diversion, port congestion, equipment scarcity, D&D exposure, transit-risk insurance). Every component is computed by its own modeled engine and folded in transparently (the breakdown is shown). Indicative decision support — not a booking or a quote (regla 7). 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, UN/LOCODE, or 'City, Country').
dest_portYesDestination port (city, UN/LOCODE, or 'City, Country').
valueYesMerchandise value (USD) — REQUIRED. Drives mode-choice (capital in transit), insurance and (with a product) landed cost.
container_typeNoContainer size '20ft'/'40ft'/'40HC'. Optional; defaults to '40ft'.
weight_kgNoShipment gross weight (kg) — sharpens mode-choice (air chargeable weight) and emissions. Optional.
volume_m3NoShipment volume (m³) — drives the air volumetric weight. Optional.
productNoProduct description or HS context — enables the landed-cost (duty) component. Optional.
hs_codeNoExplicit HS code (alternative to product). Optional.
urgencyNo'relaxed', 'normal' (default), 'urgent' or 'critical'. A critical/urgent shipment shifts the recommendation toward speed (air/sea-air) and a reliability-led carrier.
deadlineNoHard arrival deadline (ISO 'YYYY-MM-DD') — adds an expected-stockout cost to the mode decision. Optional.
ship_dateNoIntended ship date (ISO). Drives seasonality, congestion and the book-now call. Optional; defaults to today.
incotermNoOptional Incoterms 2020 rule (EXW…DDP) — sets who carries transit risk in the risk assessment.
carrierNoOptional preferred carrier (refines equipment & D&D).
annual_volumeNoOptional annual volume (containers) — informational for the decision context.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It details that the tool integrates multiple engines, returns recommendations, and is non-binding. It mentions premium payment but does not disclose error conditions or side effects, though for a decision support tool this is acceptable.

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

Conciseness3/5

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

The description is verbose and uses marketing language ('makes freight-pulse insustituible') and Spanish terms ('PUESTO EN DESTINO'), which reduces clarity for an English-only agent. Despite front-loading the purpose, it could be more concise and structured.

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 14 parameters, no output schema, and no annotations, the description fully explains what the tool returns (mode, carrier, timing, cost, risks) and how it works, including payment details. It is comprehensive for the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100% and the description adds significant context for parameters (e.g., 'value drives mode-choice', 'urgency shifts recommendation', 'deadline adds stockout cost'), going well beyond the schema descriptions.

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 it is the UNIFIED decision tool that integrates every freight-pulse layer into one actionable answer for a concrete shipment. It specifies output components and distinguishes from sibling tools that focus on individual layers.

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

Usage Guidelines4/5

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

The description explains input requirements and output, and notes it is 'indicative decision support — not a booking or a quote', providing context. However, it lacks explicit guidance on when to use this holistic tool versus individual layer tools from the sibling list.

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