Skip to main content
Glama

freightgate-mcp-server

Calculate Demurrage & Detention Costs

shippingrates_dd_calculate
Read-onlyIdempotent

Calculate demurrage and detention (D&D) costs for one carrier in one country.

Use this when the user needs a detailed cost breakdown for a specific carrier. Returns free days, per-diem rates for each tariff slab, and total cost. This is the core tool for logistics cost analysis — it answers "how much will I pay if my container is detained X days?"

To compare D&D costs across all carriers at once, use shippingrates_dd_compare instead.

By default this returns carrier detention/demurrage. Pass charge_type="storage" to instead get TERMINAL port storage — a distinct charge billed by the terminal, not the carrier, and never mixed into the default D&D answer. Storage coverage is thin — only a handful of carrier/country lanes have it. Any uncovered combo returns an explicit 'no data' error (never a false $0), and that error names the lanes that ARE covered, derived live from the database rather than from a hardcoded list that would go stale.

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

Returns: { line, country, container_type, days, free_days, breakdown, total_cost, currency, charge_type_served, charge_family: 'carrier_dd'|'terminal_storage' }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYesNumber of detention days
lineYesShipping line slug — maersk, msc, cmacgm (or cma-cgm), hapag-lloyd, one, cosco, zim, evergreen, yangming, hmm, arkas, oocl, pil
countryYesISO 2-letter country code (e.g. IN, AE, SG)
directionNoimport or export (default import)
x_paymentNox402 payment proof header (optional — required for paid access)
charge_typeNoOverride the charge type; default is the engine's detention→demurrage→combined priority. 'storage' is a distinct TERMINAL charge (not carrier D&D) and is ONLY ever returned when explicitly requested here — thin coverage, see tool description.
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

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. Changed2 schema fields changed
    • addedInput schema / properties / charge_type
      Added value: +{
      +  "description": "Override the charge type; default is the engine's detention→demurrage→combined priority. 'storage' is a distinct TERMINAL charge (not carrier D&D) and is ONLY ever returned when explicitly requested here — thin coverage, see tool description.",
      +  "enum": [
      +    "detention",
      +    "demurrage",
      +    "combined",
      +    "storage"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / direction
      Added value: +{
      +  "description": "import or export (default import)",
      +  "enum": [
      +    "import",
      +    "export"
      +  ],
      +  "type": "string"
      +}
  3. 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"
      +]
  4. Changed2 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"
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), it details return fields, default charge-type priority, storage coverage gaps, explicit 'no data' error behavior, live-derived error messages, payment cost, and 402 handling. No contradiction with annotations.

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?

Well-structured with clear sections: purpose, usage, comparison, storage nuance, payment, and return format. Slightly verbose in the storage sentence but every part earns its place.

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?

Despite no output schema, the description covers all decision-relevant aspects: scope, charge types, payment requirements, error semantics, and return shape. Agent has sufficient info to select and invoke correctly.

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 covers all 7 parameters (100%), so baseline is 3. Description adds meaning for charge_type='storage' override, default priority engine, and payment context, providing value beyond 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 opens with 'Calculate demurrage and detention (D&D) costs for one carrier in one country' — a specific verb, resource, and scope. It explicitly contrasts with shippingrates_dd_compare for cross-carrier comparison, making it distinct from siblings.

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?

It provides explicit guidance: 'Use this when the user needs a detailed cost breakdown for a specific carrier' and names the alternative tool for comparing all carriers. Also explains when to use charge_type='storage' and its limitations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources