Skip to main content
Glama
VesselAPI MCP Server

VesselAPI MCP Server

get_vessel_positions_batch

Retrieve current or historical positions for multiple vessels in one request using MMSI or IMO numbers, with time filters and pagination.

Instructions

Get positions for multiple vessels at once by MMSI or IMO numbers

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": {
      "ids": "<ids>"
    },
    "name": "get_vessel_positions_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesComma-separated list of MMSI or IMO numbers
limitNoResults per page, 1 to 50. Defaults to 20.
idTypeNoIdentifier type: imo (default) or mmsi
timeToNoEnd time filter in RFC3339 format (defaults to current time)
timeFromNoStart time filter in RFC3339 format (defaults to 2 hours ago)
nextTokenNoPagination token from previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / idType / enum
      Added value: +[
      +  "imo",
      +  "mmsi"
      +]
    • 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"
  3. Addedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations and no output schema, so the description carries the full burden, yet it says nothing about what a position record contains, how missing/invalid MMSIs are handled, or rate limits. The only behavioral hints (pagination, paging size, time window defaults) come from the schema, not the description.

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?

A single tight sentence with no filler and the key scope ('multiple vessels at once') front-loaded. It is efficient, though arguably too terse for a 6-parameter batch endpoint.

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 6-param batch tool with no annotations and no output schema, the description is thin: it does not characterize the returned position data or how partial failures across a batch are reported. The fully documented schema compensates for the parameter side, which keeps this at minimum-viable rather than inadequate.

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 every parameter including timeFrom/timeTo defaults and nextToken is already documented. The description adds only the note that IDs may be MMSI or IMO, which merely echoes the schema; baseline 3 applies.

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 positions') plus the batch scope ('multiple vessels at once'), which distinguishes it from a single-vessel lookup. However it never names the obvious sibling get_vessel_position, so the differentiation is implicit rather than explicit.

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?

'Multiple vessels at once' hints that this is the batch alternative to a single-position call, but there is no explicit when-to-use/when-not guidance, no mention of get_vessel_position, get_vessels_in_radius, or get_vessels_in_area, and no statement about batch size limits (e.g. how many IDs are reasonable).

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