freightgate-mcp-server

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

Name	Required	Description
`origin`	Yes	Origin port UN/LOCODE — e.g. INNSA (Nhava Sheva), CNSHA (Shanghai), SGSIN (Singapore)
`icd_code`	No	Destination ICD UN/LOCODE filter
`x_payment`	No	x402 payment proof header
`cargo_class`	No	Cargo class filter — 'general' or 'DG' (dangerous goods). Default: general.
`destination`	Yes	Destination city or ICD code
`delivery_mode`	No	Delivery mode filter — 'ramp' (ICD/CFS pickup) or 'door' (door delivery). Default: ramp — ramp and door rates are never mixed in one comparison.
`container_type`	No	Container type (default: 20GP)
`weight_bracket`	No	Weight bracket filter (e.g. standard, heavy)

Schema Changelog

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

Changed4 schema fields changedJul 7, 2026

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"
+}

Changed1 schema field changedApr 10, 2026

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)"

AddedMar 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds key behavioral details: sorted cheapest first, ramp/door rates never mixed, delivery_mode defaults to 'ramp', payment required ($0.08/call via x402), returns 402 without payment, and return format. 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.

Conciseness5/5

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

Four sentences, each earning its place: purpose, usage alternatives, payment/behavioral constraints, and return format. Front-loaded main purpose.

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?

Complete for an 8-parameter tool: covers use case, alternatives, payment, behavioral constraints, and return format. Since no output schema exists, the explicit return field list is valuable.

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 coverage is 100%; all parameters have descriptions. The description adds minimal new parameter semantics beyond the schema—it repeats delivery_mode default and mentions return fields, but does not clarify additional parameter meaning. Baseline 3 per rubric.

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?

Clearly states the tool's function: 'Compare inland haulage rates across ALL available carriers for a port-to-ICD/city pair — sorted cheapest first.' It also 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 this for carrier selection on inland legs — answers "which carrier offers the cheapest trucking/rail from port X to city Y?"' It explicitly names alternatives and when to use them, and clarifies delivery_mode behavior.

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 tools Inspect

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

Need Help?