Skip to main content
Glama
VesselAPI MCP Server

VesselAPI MCP Server

get_vessel_eta

Retrieve a vessel's most recently reported ETA from its AIS voyage data to check the declared arrival time, not a predicted estimate.

Instructions

Get the most recent ETA the vessel itself reported in its AIS voyage data. This is the declared ETA, not a prediction.

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_eta"
  }
}

Input Schema

NameRequiredDescriptionDefault
idTypeNoIdentifier type: imo (default) or mmsi
vesselIdYesVessel identifier (IMO number by default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv2.0.0
    • 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"
      +]
  3. Addedv1.3.0

TDQS

A3.8/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 that the ETA comes from the vessel's own AIS voyage data and is declared rather than predicted, but it does not cover permissions, error behavior when no ETA exists, or return format.

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 are front-loaded with the essential distinction. Every sentence adds value and there is no redundant restatement of the tool name.

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 simple two-parameter read tool with complete schema descriptions, the definition is nearly sufficient. It could say more about the ETA value format or behavior when no voyage ETA is available, but the core purpose and source are clear.

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 both parameters are already fully documented in the schema. The description adds no parameter-specific semantics beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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: getting the most recent vessel-reported ETA from AIS voyage data. It also explicitly distinguishes this from a prediction, making the tool's output unambiguous.

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 when to use it by contrasting declared ETA with predicted ETA, but it does not name explicit alternatives or state when not to use it. No sibling tool is referenced for routing.

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