Skip to main content
Glama
vessel-api

VesselAPI MCP Server

by vessel-api
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

get_port_inbound

Retrieve vessels arriving at a specified port within a custom ETA window, filtering by AIS position time range for accurate inbound tracking.

Instructions

Get vessels heading to a specific port within an ETA arrival window

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
etaToNoEnd of ETA arrival window (RFC3339). Omit to default to 72 hours ahead.
limitNoResults per page, 1 to 50. Defaults to 20.
timeToNoAIS position time range end (RFC3339 format)
etaFromNoStart of ETA arrival window (RFC3339). Omit to default to now.
timeFromNoAIS position time range start (RFC3339 format)
unlocodeYesUN/LOCODE of the destination port (e.g. NLRTM for Rotterdam)
nextTokenNoPagination token from previous response

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv2.0.0
    • changedInput schema / properties / etaFrom / description
      Previous value: -"Start of ETA arrival window (RFC3339 format, e.g. 2026-03-07T00:00:00Z)"New value: +"Start of ETA arrival window (RFC3339). Omit to default to now."
    • changedInput schema / properties / etaTo / description
      Previous value: -"End of ETA arrival window (RFC3339 format, e.g. 2026-03-14T00:00:00Z)"New value: +"End of ETA arrival window (RFC3339). Omit to default to 72 hours ahead."
    • 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"
    • changedInput schema / required
      Previous value: -[
-  "unlocode",
-  "etaFrom",
-  "etaTo"
-]New value: +[
+  "unlocode"
+]
  2. Addedv1.3.0

TDQS

A3.6/5.0
Behavior2/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 only states the high-level purpose and does not describe pagination behavior, default windows, return shape, or any safety/permission considerations. This leaves key behavioral details undisclosed.

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?

The description is a single efficient sentence with no filler. It is concise and front-loaded, though slightly too sparse to fully carry behavioral context on its own.

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 tool with 7 parameters and no output schema or annotations, the description alone is only minimally complete. It states the core use case, and the schema supplies parameter details, but return behavior, pagination semantics, and the meaning of the AIS time range in the overall flow are not described.

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?

The input schema covers 100% of the parameters with useful descriptions, including defaults, ranges, and RFC3339 formats. The description itself adds little beyond the schema, so the baseline moderate score is appropriate.

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?

The description uses a specific verb and resource: 'Get vessels heading to a specific port within an ETA arrival window.' This clearly defines the tool's scope and distinguishes it from sibling tools that focus on individual vessels, positions, or port events.

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

Usage Guidelines4/5

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

The description provides a clear usage context: querying port-bound vessels by ETA window. It does not explicitly list alternatives or exclusions, but the stated port-and-ETA focus gives enough direction to choose this tool over vessel-position or port-event siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vessel-api/vesselapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server