VesselAPI MCP Server

Overview Schema Source Related Servers Discussions Admin

list_port_events

Retrieve port arrivals and departures across covered ports, filtered by time, country, port, vessel, or event type; defaults to the last 2 hours unless a start time is provided.

Instructions

List port events (arrivals/departures) across all covered ports, with optional filters for time, country, port, vessel, or event type. Covers only the last 2 hours unless timeFrom is given. Events are kept for 31 days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_port_events"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Results per page, 1 to 50. Defaults to 20.
`timeTo`	No	End of the time window, RFC3339. Defaults to now.
`country`	No	Filter by port country (case-insensitive)
`portName`	No	Filter by port name (full-text search)
`timeFrom`	No	Start of the time window, RFC3339. Without it the service returns only the last 2 hours.
`unlocode`	No	Filter by port UN/LOCODE
`eventType`	No	Filter by event type. Omit for both arrivals and departures
`nextToken`	No	Pagination token from previous response
`vesselName`	No	Filter by vessel name (full-text search)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.2.0Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / timeFrom / description

Previous value: -"Start time (RFC3339 format)"New value: +"Start of the time window, RFC3339. Without it the service returns only the last 2 hours."

changedInput schema / properties / timeTo / description

Previous value: -"End time (RFC3339 format)"New value: +"End of the time window, RFC3339. Defaults to now."

Changed6 schema fields changedv2.0.0Aug 20, 2026

changedInput schema / properties / eventType / description

Previous value: -"Filter by event type (arrival, departure)"New value: +"Filter by event type. Omit for both arrivals and departures"

addedInput schema / properties / eventType / enum

Added value: +[
+  "arrival",
+  "departure",
+  "all"
+]

changedInput schema / properties / limit / description

Previous value: -"Max results per page"New value: +"Results per page, 1 to 50. Defaults to 20."

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

Addedv1.3.0May 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description does real work: it discloses the non-obvious default 2-hour window and the 31-day retention limit, both of which materially affect how an agent must call it. It omits pagination behavior and response shape, but the two disclosures are genuinely valuable context beyond the schema.

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?

Three short sentences with no waste: purpose first, then filters, then the two behavioral constraints. Front-loaded and easy to scan.

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 9-parameter read tool with no annotations and no output schema, the description covers scope, time-window defaults, and retention. The remaining gap is that it doesn't hint at the shape of returned events or how pagination interacts with the time window, but nothing critical to calling it correctly is missing.

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%, so every parameter is already documented, including the enum and the timeFrom default. The description only restates the filter categories without adding format or interaction details, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('List port events (arrivals/departures)') with a clear scope that differentiates it: 'across all covered ports', implying it is not scoped to a single port as get_port_events or search_port_events_by_port would be. However, it never names those close siblings explicitly, so the agent must infer the routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the scope phrase 'across all covered ports', which steers away from port-specific siblings, but there is no explicit when-to-use/when-not or named alternative. The 'last 2 hours unless timeFrom is given' note is a useful caveat rather than a selection guideline.

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