VesselAPI MCP Server

Overview Schema Source Related Servers Discussions Admin

get_port_events

Retrieve arrivals and departures for a specific port, with optional time-window and pagination filters; without a start time, returns only the last two hours.

Instructions

Get port events (arrivals/departures) for a specific port. Covers only the last 2 hours unless timeFrom is given.

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": {
      "unlocode": "<unlocode>"
    },
    "name": "get_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.
`timeFrom`	No	Start of the time window, RFC3339. Without it the service returns only the last 2 hours.
`unlocode`	Yes	UN/LOCODE of the port
`nextToken`	No	Pagination token from previous response

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Oct 30, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed6 schema fields changedv2.0.0Aug 20, 2026

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"

addedInput schema / properties / timeFrom

Added value: +{
+  "description": "Start of the time window, RFC3339. Without it the service returns only the last 2 hours.",
+  "type": "string"
+}

addedInput schema / properties / timeTo

Added value: +{
+  "description": "End of the time window, RFC3339. Defaults to now.",
+  "type": "string"
+}

Addedv1.3.0May 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the default time window ('only the last 2 hours unless timeFrom is given'), but says nothing about pagination behavior, event payload contents, permissions, or rate limits.

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?

Two short sentences, front-loaded with the core purpose and followed by the most important behavioral constraint. Every sentence earns its place with no filler.

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

Completeness3/5

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

With no annotations and no output schema, the description should do more to explain the shape of returned events and pagination behavior. It is adequate for identifying the tool but leaves meaningful gaps for an agent operating without structured safety or return metadata.

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 all five parameters are already documented in the schema. The description restates the timeFrom default behavior but adds no meaning beyond what the schema already specifies; baseline 3 is appropriate.

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?

States a specific verb and resource ('Get port events') and clarifies what data is returned (arrivals/departures) for a single port. However, it does not distinguish itself from close siblings such as list_port_events, search_port_events_by_port, or get_port_events_by_vessel.

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?

The description implies usage context (a specific port, recent events) and mentions the timeFrom condition, but gives no explicit guidance on when to prefer this over sibling tools like search_port_events_by_port or list_port_events.

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