Skip to main content
Glama

freightgate-mcp-server

by io.github.vinaybhosle
OverviewAdmin

Published Total-Cost Estimate

shippingrates_total_cost
Read-onlyIdempotent

Calculate a published multi-component shipping-cost estimate from certified dependencies: freight benchmark observations when available, surcharges, origin/destination local charges, requested demurrage/detention exposure, FX, and transit context.

The result can be partial. A market index is not a carrier quote, and a missing component is counted as zero only when the response explicitly reports the gap. Always inspect coverage, data_gaps, total_is_partial, warning, and each component's verified flag before quoting the result. For individual components, use shippingrates_rates, shippingrates_surcharges, shippingrates_local_charges, and shippingrates_dd_calculate.

PAID: $0.15/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions.

Returns: { components: { freight: { amount, currency, basis, verified }, origin_local_charges / destination_local_charges: { port, items: [{ charge, amount, currency, charge_type ('mandatory'|'additional'), charge_type_reason? }], total, mandatory_total, additional_total, currency: 'INR', verified }, surcharges: { items, total, verified }, detention_demurrage? }, coverage, data_gaps?, transit_days, total_estimated_cost_usd, total_estimated_cost_inr, totals_basis: 'mandatory_only', total_additional_cost_usd/inr, total_all_inclusive_cost_usd/inr }.

IMPORTANT: the headline total_estimated_cost_* sums MANDATORY charges only (freight, lane surcharges, mandatory local charges, requested D&D). Conditional/if-applicable fees (amendments, penalties, cargo-type surcharges) are excluded from the headline — they are itemized with charge_type='additional' and summed in total_additional_cost_*; total_all_inclusive_cost_* is the sum of both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineYesShipping line slug — maersk, msc, cmacgm (or cma-cgm), hapag-lloyd, one, cosco, zim, evergreen, yangming, hmm, arkas, oocl, pil
originYesOrigin port UN/LOCODE — e.g. INNSA (Nhava Sheva), CNSHA (Shanghai), SGSIN (Singapore)
x_paymentNox402 payment proof header
destinationYesDestination port or inland location
container_typeYesISO 6346 container type — 20GP, 40GP, 40HC, 20RF, 40RF, 20OT, 40OT, 45HC, 40FR, 20FR, 40DG, 20DG, 45RF, 45OT, 45DG, 40TK, 20TK, 45GP, 45TK, 40NOR
detention_daysNoExpected detention days (default: 0)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / line / enum
      Previous value: -[
-  "maersk",
-  "msc",
-  "cmacgm",
-  "cma-cgm",
-  "hapag-lloyd",
-  "one",
-  "cosco",
-  "zim",
-  "evergreen",
-  "yangming",
-  "hmm",
-  "arkas",
-  "oocl",
-  "pil"
-]New value: +[
+  "maersk",
+  "msc",
+  "cmacgm",
+  "cma-cgm",
+  "hapag-lloyd",
+  "one",
+  "cosco",
+  "zim",
+  "evergreen",
+  "yangming",
+  "hmm",
+  "arkas",
+  "oocl",
+  "pil",
+  "wanhai"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / container_type / description
      Previous value: -"ISO 6346 container type — 20DV, 40DV, 40HC, 20RF, 40RF, 20OT, 40OT, 20FR, 40FR"New value: +"ISO 6346 container type — 20GP, 40GP, 40HC, 20RF, 40RF, 20OT, 40OT, 45HC, 40FR, 20FR, 40DG, 20DG, 45RF, 45OT, 45DG, 40TK, 20TK, 45GP, 45TK, 40NOR"
    • changedInput schema / properties / container_type / enum
      Previous value: -[
-  "20DV",
-  "40DV",
-  "40HC",
-  "20RF",
-  "40RF",
-  "20OT",
-  "40OT",
-  "20FR",
-  "40FR"
-]New value: +[
+  "20GP",
+  "40GP",
+  "40HC",
+  "20RF",
+  "40RF",
+  "20OT",
+  "40OT",
+  "45HC",
+  "40FR",
+  "20FR",
+  "40DG",
+  "20DG",
+  "45RF",
+  "45OT",
+  "45DG",
+  "40TK",
+  "20TK",
+  "45GP",
+  "45TK",
+  "40NOR"
+]
    • changedInput schema / properties / line / description
      Previous value: -"Shipping line slug — one of: maersk, msc, cma-cgm, hapag-lloyd, one, cosco"New value: +"Shipping line slug — maersk, msc, cmacgm (or cma-cgm), hapag-lloyd, one, cosco, zim, evergreen, yangming, hmm, arkas, oocl, pil"
    • changedInput schema / properties / line / enum
      Previous value: -[
-  "maersk",
-  "msc",
-  "cma-cgm",
-  "hapag-lloyd",
-  "one",
-  "cosco"
-]New value: +[
+  "maersk",
+  "msc",
+  "cmacgm",
+  "cma-cgm",
+  "hapag-lloyd",
+  "one",
+  "cosco",
+  "zim",
+  "evergreen",
+  "yangming",
+  "hmm",
+  "arkas",
+  "oocl",
+  "pil"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / container_type / description
      Previous value: -"Container type code"New value: +"ISO 6346 container type — 20DV, 40DV, 40HC, 20RF, 40RF, 20OT, 40OT, 20FR, 40FR"
    • changedInput schema / properties / line / description
      Previous value: -"Shipping line slug"New value: +"Shipping line slug — one of: maersk, msc, cma-cgm, hapag-lloyd, one, cosco"
    • changedInput schema / properties / origin / description
      Previous value: -"Origin port UN/LOCODE"New value: +"Origin port UN/LOCODE — e.g. INNSA (Nhava Sheva), CNSHA (Shanghai), SGSIN (Singapore)"
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses critical behavioral traits: partial results, market index vs. carrier quote distinction, mandatory vs. additional cost categorization, and the 402 payment failure mode. This is rich, non-obvious context that annotations alone do not provide.

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

Conciseness5/5

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

The description is long but every sentence earns its place: purpose, rationale, payment, output structure, and an IMPORTANT clarification. It is front-loaded with the core function and then layers caveats and details in a logical order, making it appropriately sized for the tool's complexity.

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?

For a tool with no output schema, the description fully compensates by explaining the return shape, covering key fields, and highlighting the mandatory vs. additional cost distinction. It also addresses partial results and the need to inspect verification flags, making it self-sufficient for an agent to understand what to expect and how to interpret results.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description does not add substantial per-parameter meaning beyond translating 'demurrage/detention exposure' to the detention_days parameter, but the schema already fully documents each parameter with descriptions and enums.

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 opens with a specific verb ('Calculate') and a well-defined resource ('published multi-component shipping-cost estimate'), listing the exact components included. It also distinguishes itself from siblings by pointing to individual component tools for specific needs.

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 says 'For individual components, use shippingrates_rates, shippingrates_surcharges, shippingrates_local_charges, and shippingrates_dd_calculate,' providing clear alternatives. Also notes the payment requirement and cautions that the result can be partial, establishing appropriate usage expectations.

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

All freightgate-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources