Skip to main content
Glama

freightgate-mcp-server

by io.github.vinaybhosle
OverviewAdmin

Published Freight Benchmarks

shippingrates_rates
Read-onlyIdempotent

Get current certified freight benchmark observations between two ports, optionally filtered by container type.

These are official published market indices, not carrier spot quotes or contracted rates. An unsupported lane returns an empty rates array. For a published multi-component estimate, use shippingrates_total_cost and inspect its coverage, data_gaps, and total_is_partial fields.

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

Returns: { route, rates: [{ trade_lane_name, origin_port, origin_region, destination_port, destination_region, container_type, rate_low, rate_mid, rate_high, currency, index_source, trend, week_over_week_change_pct, rate_date }], carriers, transit_days_min, transit_days_max, rate_low?, rate_mid?, rate_high?, trend?, currency? }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesOrigin port UN/LOCODE — e.g. INNSA (Nhava Sheva), CNSHA (Shanghai), SGSIN (Singapore)
x_paymentNox402 payment proof header
destinationYesDestination port UN/LOCODE — e.g. AEJEA (Jebel Ali), NLRTM (Rotterdam), USNYC (New York)
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
    • changedInput schema / properties / container_type / description
      Previous value: -"Container type filter"New value: +"Container type filter — e.g. 20DV, 40HC, 20RF"
    • changedInput schema / properties / destination / description
      Previous value: -"Destination port UN/LOCODE"New value: +"Destination port UN/LOCODE — e.g. AEJEA (Jebel Ali), NLRTM (Rotterdam), USNYC (New York)"
    • 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.4/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds valuable behavioral context: payment requirement ($0.03/call via x402), 402 error response without payment, and fallback behavior for unsupported lanes. It also documents the return structure, which is essential since no output schema exists.

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?

The description is well-structured: a clear first sentence, then context, payment, and return format. It avoids unnecessary prose. The long return type listing is justified by the lack of an output schema and provides essential information for the agent.

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's complexity (payment, optional filter, detailed return shape), the description covers all critical aspects: purpose, payment, error behavior, unsupported lanes, and return format. It also gives an alternative when a different type of estimate is needed. This is sufficient for an agent to invoke correctly.

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?

All parameters have descriptions in the input schema (100% coverage), including UN/LOCODE examples and container type filter. The description's 'between two ports' and 'optionally filtered by container type' align with but do not significantly extend the schema. With full schema coverage, baseline 3 is appropriate.

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 current certified freight benchmark observations between two ports, optionally filtered by container type' — a precise verb and resource. It further distinguishes itself by clarifying these are 'official published market indices, not carrier spot quotes or contracted rates' and explicitly points to shippingrates_total_cost as the alternative for multi-component estimates.

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 when-to-use context (benchmark observations between ports), what it is not (spot quotes/contracted rates), and names a specific alternative for multi-component estimates (shippingrates_total_cost). It also tells the agent that unsupported lanes return an empty rates array, helping set expectations.

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