VesselAPI MCP Server

Overview Schema Source Related Servers Discussions Admin

get_vessel_last_port_event

Retrieve a vessel's recent port arrival or departure event by IMO or MMSI to check current port activity and movement history.

Instructions

Get the most recent port event (arrival or departure) for a vessel

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": {
      "vesselId": "<vesselId>"
    },
    "name": "get_vessel_last_port_event"
  }
}

Input Schema

Name	Required	Description	Default
`idType`	No	Identifier type: imo (default) or mmsi
`vesselId`	Yes	Vessel identifier (IMO number by default)

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed2 schema fields changedv2.0.0Aug 20, 2026

changedInput schema / properties / idType / description

Previous value: -"Identifier type: imo (default), mmsi, or vesselId"New value: +"Identifier type: imo (default) or mmsi"

addedInput schema / properties / idType / enum
```
Added value: +[
+  "imo",
+  "mmsi"
+]
```

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 supplied, so the description must carry the behavioral burden. 'Get' implies a read-only lookup and 'most recent' implies at most one result, but it does not say what happens when no events exist, whether results are cached/live, or what the response contains. It covers the basic shape but leaves real gaps for a zero-annotation tool.

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?

A single front-loaded sentence with no filler; the resource and the 'most recent' qualifier come before any extra detail. Nothing extraneous.

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?

For a simple two-parameter read tool with no output schema, the description covers the core intent. However, with no annotations and no output schema, the agent is left guessing about the empty-result case and the returned event's fields, which the description could reasonably have summarized.

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%: vesselId and the idType enum (imo default / mmsi) are fully documented in the schema, so the 3 baseline applies. The description adds no format or default guidance for these parameters beyond what's already structured.

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?

The description gives a specific verb ('Get') and resource ('most recent port event (arrival or departure) for a vessel'), which is precise enough to distinguish it from list-style siblings like list_port_events or get_port_events_by_vessel. It stops short of naming those siblings explicitly, but 'most recent ... event' singular clearly separates it from the retrieval-many tools.

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 only implied by the phrase 'most recent', which suggests a single-result lookup rather than a historical listing. There is no explicit statement of when to prefer this over get_port_events_by_vessel or search_port_events_by_vessel, and no prerequisites or fallback behavior mentioned.

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