Skip to main content
Glama

ShippingRates MCP Server (Apify)

by actor.apify.vinaybhosle--shippingrates-mcp

Vessel Schedule

shippingrates_vessel_schedule
Read-onlyIdempotent

Get upcoming vessel arrivals and departures at a specific port.

Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes.

For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules.

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

Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portYesUN/LOCODE port code — e.g. INNSA (Nhava Sheva), AEJEA (Jebel Ali), SGSIN (Singapore)
x_paymentNox402 payment proof header
days_aheadNoDays to look ahead (default: 14)

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds payment requirement and 402 response behavior, which is beyond annotations and valuable for agent decision-making.

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?

Concise two-paragraph structure with front-loaded purpose, efficient use of words, no 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?

Despite no output schema, description enumerates return fields, covers payment context, and no missing information for this tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with descriptions. Description reinforces default for days_ahead (14) and explains x_payment header usage, adding clarity beyond 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?

Description clearly states 'Get upcoming vessel arrivals and departures at a specific port' with specific verb+resource. It differentiates from sibling tools shippingrates_transit and shippingrates_transit_schedules.

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?

Explicitly provides when to use this tool for booking planning and tracking, and when-not to use it, referencing alternatives for transit times and detailed routing.

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 (Apify) 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.6/5.0
Disambiguation5/5

All 26 tools have clearly distinct purposes, with detailed descriptions that differentiate overlapping areas (e.g., transit vs. schedule vs. vessel schedule). Even closely related tools like dd_calculate, dd_compare, and dd_countdown are well-delineated.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with prefix 'shippingrates_'. Compound names use underscores predictably (e.g., dd_calculate, inland_compare, vessel_schedule_options), making the naming scheme highly predictable.

Tool Count4/5

26 tools is slightly above the ideal range, but the breadth of features (rates, D&D, inland, congestion, risk, schedules, etc.) justifies the count. Each tool earns its place, and there is minimal bloat.

Completeness5/5

The tool set covers all major aspects of shipping intelligence: rates, surcharges, local charges, D&D, inland haulage, congestion, risk, transit, schedules, regulatory updates, and discovery tools. No obvious gaps for the stated purpose.

Resources