mcp-livedatapro

getContainerFreightRates

Spot ocean freight rates for 20ft and 40ft (FEU) containers between global trade lanes. Use when quoting port-to-port commercial ocean container spot rates (20ft TEU, 40ft FEU, Reefer) in USD between maritime trade lanes. Do not use for small parcel courier shipping (use getCourierShippingRates) or port berth wait times (use getPortCongestion). Returns current spot index including bunker surcharge flags.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "origin_port": "<origin_port>",
      "destination_port": "<destination_port>"
    },
    "name": "getContainerFreightRates"
  }
}

Input Schema

Name	Required	Description	Default
`origin_port`	Yes	Origin seaport name or 5-letter UN/LOCODE (e.g., CNSHA for Shanghai).
`destination_port`	Yes	Destination seaport name or 5-letter UN/LOCODE (e.g., NLRTM for Rotterdam).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / destination_port / examples
```
Added value: +[
+  "NLRTM"
+]
```
- addedInput schema / properties / destination_port / minLength
```
Added value: +3
```
- addedInput schema / properties / origin_port / examples
```
Added value: +[
+  "CNSHA"
+]
```
- addedInput schema / properties / origin_port / minLength
```
Added value: +3
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / destination_port / description

Previous value: -"Destination port name or UN/LOCODE (e.g., NLRTM)"New value: +"Destination seaport name or 5-letter UN/LOCODE (e.g., NLRTM for Rotterdam)."

changedInput schema / properties / origin_port / description

Previous value: -"Origin port name or UN/LOCODE (e.g., CNSHA)"New value: +"Origin seaport name or 5-letter UN/LOCODE (e.g., CNSHA for Shanghai)."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the rate type, container coverage, currency, and that the response includes bunker surcharge flags, but it omits important operational context such as data freshness, rate validity period, and any access constraints.

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 front-loaded with purpose, then usage guidance, then return information. It is efficient overall, though the 20ft/40ft container types are restated in both the first and second sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only rate lookup with no output schema, the description gives enough context to call the tool correctly and understand the high-level return. A minor gap remains around data freshness and rate validity, which matters for pricing use cases.

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%, and both parameters are documented with UN/LOCODE guidance and examples. The description only reinforces port-to-port scope and does not add syntax or format meaning beyond the schema, so the high-coverage baseline of 3 applies.

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 states a specific resource and scope: spot ocean freight rates for 20ft and 40ft containers across global trade lanes. It also clearly distinguishes the tool from courier shipping and port congestion, so an agent can identify it without checking siblings.

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 explicitly says when to use the tool: quoting port-to-port commercial ocean container spot rates in USD. It also names two alternatives and the cases they cover, removing ambiguity about sibling selection.

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

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?