Skip to main content
Glama

ShippingRates MCP Server

by io.github.vinaybhosle

Shipping Surcharges

shippingrates_surcharges
Read-onlyIdempotent

Get carrier-specific surcharges — BAF (Bunker Adjustment Factor), CAF (Currency Adjustment Factor), PSS (Peak Season Surcharge), EBS (Emergency Bunker Surcharge), and more.

Use this to understand surcharge exposure for a carrier in a specific country/direction. These are charges added on top of base freight rates. For a complete cost breakdown, use shippingrates_total_cost which includes surcharges automatically.

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

Returns: Array of { surcharge_type, surcharge_name, amount, currency, per_unit, effective_from, effective_to, direction }.

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
countryNoISO 2-letter country code
directionNoTrade direction — 'import' or 'export'
x_paymentNox402 payment proof header

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
    • 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. Changed2 schema fields changed
    • changedInput schema / properties / direction / description
      Previous value: -"Trade direction"New value: +"Trade direction — 'import' or 'export'"
    • 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"
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only and idempotent behavior, but the description adds crucial context: a paid API with a specific cost ('PAID: $0.02/call via x402') and an exact error condition ('Without payment, returns 402 with payment instructions'). It also discloses the return structure, which is essential given no output schema.

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 concise yet complete: three short paragraphs cover purpose, usage guidance, payment, and return format. Every sentence serves a purpose, and the front-loaded opening makes the tool's function immediately clear.

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 and only one required parameter, the description provides a full picture: what the tool does, when to use it, payment requirements, error behavior, and the shape of the return array. No critical information seems missing.

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 extra parameter details beyond what the schema provides, but it does contextualize the country/direction filters without needing to repeat enum definitions. This is sufficient.

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 'Get carrier-specific surcharges' and lists specific types (BAF, CAF, PSS, EBS), clearly identifying the tool's function. It distinguishes itself from the sibling tool shippingrates_total_cost by noting that this tool focuses on surcharges only, making the purpose unambiguous.

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?

Explicit usage context is provided: 'Use this to understand surcharge exposure for a carrier in a specific country/direction.' It also gives a clear alternative: 'For a complete cost breakdown, use shippingrates_total_cost which includes surcharges automatically,' effectively stating when not to use this tool.

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

All ShippingRates 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.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: D&D calculator/compare/countdown, inland search/haulage/compare, and congestion/news/risk are well separated. However, the transit/vessel group (transit, transit_schedules, vessel_schedule, vessel_schedule_options) and rates vs total_cost could cause some selection ambiguity, though descriptions help differentiate them.

Naming Consistency3/5

All tools share the 'shippingrates_' prefix and snake_case, but naming patterns vary: some are action-oriented (shippingrates_dd_calculate, shippingrates_inland_compare), while others are noun phrases (shippingrates_surcharges, shippingrates_port, shippingrates_total_cost). This inconsistency could make it harder to predict tool names.

Tool Count3/5

With 26 tools, the server is on the heavier side, exceeding the typical 15-tool comfort zone. However, the broad domain of shipping rates, logistics, and regulatory data justifies the number, as each tool covers a distinct aspect. Still, the volume may overwhelm agents.

Completeness5/5

The tool set is remarkably comprehensive for a shipping rates server, covering freight benchmarks, surcharges, local charges, D&D (calculate/compare/countdown), inland haulage, transit schedules, vessel schedules, congestion, risk scoring, regulatory updates, facilities, FX, and a composite total-cost calculator. No obvious gaps for common logistics cost-analysis workflows.

Resources