Skip to main content
Glama

freightgate-mcp-server

by io.github.vinaybhosle
OverviewAdmin

Get Inland Haulage Rates

shippingrates_inland_haulage
Read-onlyIdempotent

Get inland haulage (trucking/rail) rates for moving containers between a port and an inland location.

Use this when you know the specific origin port and destination and need rate quotes. Returns route-specific rates by container type including base rate, fuel surcharges, and estimated transit times.

To discover what routes exist first, use shippingrates_inland_search. To compare rates across all carriers for the same route, use shippingrates_inland_compare.

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

Returns: Array of { carrier, origin, destination, container_type, rate, fuel_surcharge, total, currency, transit_days, mode, delivery_mode, icd_code }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoTransport mode filter (PRE or ONC)
originYesOrigin port UN/LOCODE (e.g. INNSA, INMAA)
icd_codeNoDestination ICD UN/LOCODE filter
x_paymentNox402 payment proof header
cargo_classNoCargo class filter — 'general' or 'DG' (dangerous goods). Default: general.
destinationYesInland destination city name (e.g. Ahmedabad, Delhi)
delivery_modeNoDelivery mode filter — 'ramp' (ICD/CFS pickup) or 'door' (door delivery). Default: ramp.
container_typeNoContainer type filter — e.g. 20DV, 40HC, 20RF

Schema Changelog

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

  1. Changed1 schema field changed
    • 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"
+]
  2. Changed3 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.",
+  "enum": [
+    "ramp",
+    "door"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / icd_code
      Added value: +{
+  "description": "Destination ICD UN/LOCODE filter",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / container_type / description
      Previous value: -"Container type filter"New value: +"Container type filter — e.g. 20DV, 40HC, 20RF"
  4. Changed6 schema fields changed
    • removedInput schema / properties / country
      Removed value: -{
-  "description": "ISO 2-letter country code",
-  "maxLength": 2,
-  "minLength": 2,
-  "type": "string"
-}
    • addedInput schema / properties / destination
      Added value: +{
+  "description": "Inland destination city name (e.g. Ahmedabad, Delhi)",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / line
      Removed value: -{
-  "description": "Shipping line slug",
-  "enum": [
-    "maersk",
-    "msc",
-    "cma-cgm",
-    "hapag-lloyd",
-    "one",
-    "cosco"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "Transport mode filter (PRE or ONC)",
+  "type": "string"
+}
    • addedInput schema / properties / origin
      Added value: +{
+  "description": "Origin port UN/LOCODE (e.g. INNSA, INMAA)",
+  "maxLength": 10,
+  "minLength": 2,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "line",
-  "country"
-]New value: +[
+  "origin",
+  "destination"
+]
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses critical behavioral traits: the payment requirement ($0.05/call via x402), the consequence of non-payment (returns 402 with payment instructions), and the return payload structure. This adds substantial context that annotations do not cover, such as the exact array fields and the fact that rates are route-specific.

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 and well-structured: it opens with a clear purpose, then gives usage context, lists alternatives, states the payment/error behavior, and ends with the return format. Every sentence provides actionable information without redundancy or filler.

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 the tool has 8 parameters and no output schema, the description adequately compensates by providing the output array shape, clarifying the payment flow, and explaining how this tool fits with its siblings. It is complete enough for an agent to select and invoke the tool correctly without needing additional documentation.

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?

The input schema already has 100% description coverage for all 8 parameters, including enums and examples. The description adds minimal extra meaning, merely reinforcing that origin and destination are the required route identifiers and mentioning container type in prose. This matches the baseline of 3 for high schema coverage; it does not meaningfully compensate or elaborate beyond the schema.

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 the tool's verb, resource, and scope: 'Get inland haulage (trucking/rail) rates for moving containers between a port and an inland location.' It also explicitly distinguishes itself from sibling tools by naming shippingrates_inland_search and shippingrates_inland_compare, 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?

The description provides explicit usage guidance: 'Use this when you know the specific origin port and destination and need rate quotes.' It also tells when to use alternatives: 'To discover what routes exist first, use shippingrates_inland_search. To compare rates across all carriers for the same route, use shippingrates_inland_compare.' This fully addresses both when-to-use and when-not-to-use.

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