VesselAPI MCP Server

by vessel-api

Overview Schema Source Related Servers Discussions Admin

TypeScript

search_port_events_by_vessel

Search port events for a named vessel; results cover the last two hours unless a timeFrom start is provided.

Instructions

Search port events by vessel name. 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": {
      "vesselName": "<vesselName>"
    },
    "name": "search_port_events_by_vessel"
  }
}

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.
`nextToken`	No	Pagination token from previous response
`vesselName`	Yes	Vessel name to search for

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.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the default 2-hour time window, which an agent could otherwise miss, but says nothing about return format, whether this is a read-only/paginated operation, or result ordering.

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 tight sentences with zero waste, and the critical scoping constraint is front-loaded right after the purpose statement.

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 5-parameter, fully-schema-documented search tool, the description covers purpose and the key default behavior. The only gap is that, with no output schema, it does not describe the shape of returned events at all.

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 the baseline is 3. The description's note about timeFrom defaulting to a 2-hour window essentially restates what the schema already documents, adding no new meaning about the parameters.

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 names a specific verb ('Search'), resource ('port events'), and facet ('by vessel name'), which implicitly distinguishes it from siblings like search_port_events_by_port and list_port_events. It stops short of explicitly naming those alternatives, so it earns a 4 rather than a 5.

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 2-hour default window is a useful usage constraint, but the description gives no guidance on when to choose this tool over search_port_events_by_port, get_port_events_by_vessel, or list_port_events. The usage context is implied by the tool name rather than stated.

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