Skip to main content
Glama

ShippingRates MCP Server

by io.github.vinaybhosle

Compare Inland Haulage Rates

shippingrates_inland_compare
Read-onlyIdempotent

Compare inland haulage rates across ALL available carriers for a port-to-ICD/city pair — sorted cheapest first.

Use this for carrier selection on inland legs — answers "which carrier offers the cheapest trucking/rail from port X to city Y?" For a single carrier's rates, use shippingrates_inland_haulage instead. To discover what routes exist, use shippingrates_inland_search first.

Ramp (ICD/CFS pickup) and door delivery rates are never mixed in one comparison — delivery_mode defaults to 'ramp'. Set delivery_mode='door' to compare door-delivery rates instead.

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

Returns: Array of { carrier, mode, container_type, rate, currency, transit_days, weight_bracket, delivery_mode, icd_code } sorted by rate ascending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesOrigin port UN/LOCODE — e.g. INNSA (Nhava Sheva), CNSHA (Shanghai), SGSIN (Singapore)
icd_codeNoDestination ICD UN/LOCODE filter
x_paymentNox402 payment proof header
cargo_classNoCargo class filter — 'general' or 'DG' (dangerous goods). Default: general.
destinationYesDestination city or ICD code
delivery_modeNoDelivery mode filter — 'ramp' (ICD/CFS pickup) or 'door' (door delivery). Default: ramp — ramp and door rates are never mixed in one comparison.
container_typeNoContainer type (default: 20GP)
weight_bracketNoWeight bracket filter (e.g. standard, heavy)

Schema Changelog

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

  1. Changed4 schema fields changed
    • addedInput schema / properties / cargo_class
      Added value: +{
+  "description": "Cargo class filter — 'general' or 'DG' (dangerous goods). Default: general.",
+  "enum": [
+    "general",
+    "DG"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / delivery_mode
      Added value: +{
+  "description": "Delivery mode filter — 'ramp' (ICD/CFS pickup) or 'door' (door delivery). Default: ramp — ramp and door rates are never mixed in one comparison.",
+  "enum": [
+    "ramp",
+    "door"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / icd_code
      Added value: +{
+  "description": "Destination ICD UN/LOCODE filter",
+  "type": "string"
+}
    • addedInput schema / properties / weight_bracket
      Added value: +{
+  "description": "Weight bracket filter (e.g. standard, heavy)",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • 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)"
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds critical context: ramp and door rates are never mixed in one comparison, payment is required ($0.08/call via x402) with a 402 on failure, and the exact return array structure sorted by rate ascending. This goes well beyond the annotations.

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 front-loaded with the core purpose, then flows logically through usage guidance, alternatives, key behavioral constraint, payment info, and return format. Every sentence earns its place; there is no filler or redundancy.

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 no output schema, the description fully explains the return format (array of specific fields sorted ascending). It also covers payment, delivery_mode behavior, and when to use, making it complete for a tool with 8 parameters and complex sibling relationships.

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 baseline is 3. The description adds no new parameter semantics beyond the schema; it repeats the delivery_mode default and provides an example origin value, but these are already in the schema. No additional meaning is provided.

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?

Description explicitly states it compares inland haulage rates across ALL carriers for a port-to-ICD/city pair, sorted cheapest first. It distinguishes from siblings by naming shippingrates_inland_haulage for single-carrier rates and shippingrates_inland_search for route discovery.

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?

Provides explicit usage guidance: use for carrier selection on inland legs, with clear when-not instructions and named alternatives (single carrier → inland_haulage, route discovery → inland_search). Also explains the delivery_mode default and payment requirement.

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