SiteCheck Trade & Energy

Recorded daily port calls at one port by ship type

logistics_port_call_schedule

Read-only

Recorded daily port calls (vessel arrivals) at one port by ship type, from IMF PortWatch (AIS-derived), for the most recent days. These are past calls, not a forward arrival or departure schedule, and the latest date lags real time. Related tools on this server, for a different need: logistics_port_congestion_index when you need weekly port congestion figures for one port from Portcast's; logistics_dry_port_inland_depot when you need Inland container depots and dry ports by country. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "port": "<port>"
    },
    "name": "logistics_port_call_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	1 to 30 (default 7)
`port`	Yes	PortWatch port name, e.g. Rotterdam, Singapore

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses non-obvious behavior: the data is AIS-derived, the latest date lags real time, the records are historical rather than forward-looking, and each successful call costs $0.002 USDC via x402 on Base, Solana, or Arc with failures uncharged. The payment and freshness disclosures are exactly the kind of context annotations cannot carry.

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?

Front-loaded with the core purpose and the freshness caveat, then alternatives, then pricing — a sensible priority order with no filler. Slight deductions for a long single run-on closing sentence and the dangling possessive in "from Portcast's".

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?

An output schema exists, so return structure needn't be explained, and annotations cover the read-only/open-world profile. The description still covers the remaining unknowns an agent needs — data source, staleness, historical-only scope, and cost model.

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% — 'port' already carries a PortWatch name example and 'days' already states 1 to 30 with a default of 7. The description adds the notion of a single-port scope but no syntax, naming, or edge-case guidance beyond the schema, so the baseline 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?

States a specific verb and resource ('Recorded daily port calls (vessel arrivals) at one port by ship type'), the data provenance (IMF PortWatch, AIS-derived), and explicitly negates a likely misreading ('past calls, not a forward arrival or departure schedule'). An agent can distinguish it from logistics_port_congestion_index and logistics_dry_port_inland_depot without opening any schema.

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?

Gives explicit routing: use this for recorded daily calls at one port, use logistics_port_congestion_index for weekly congestion figures from Portcast, use logistics_dry_port_inland_depot for inland depots by country. Each alternative is paired with the condition that selects it.

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

All SiteCheck Trade & Energy 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?