Skip to main content
Glama

Datalastic Vessel Tracking & Maritime Intelligence

Get vessel position (enriched)

get_vessel_pro

Richer, heavier variant of get_vessel for a single vessel, identified by exactly one of: MMSI (9 digits), IMO (7 digits), or Datalastic UUID. In addition to the basic position and identity, it returns the recognized destination port and origin port (name + UNLOCODE), the actual time of departure (ATD), a reliable estimated time of arrival (ETA), and current draught. Prefer get_vessel for ordinary position or identity lookups; use get_vessel_pro only when the user asks about the destination or origin port, departure time, arrival time or ETA, or draught, as it is heavier on the backend. If the last known position is stale (the vessel may be out of terrestrial AIS range) and it has a destination and ETA, consider offering estimated_vessel_position to estimate where it is now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imoNoVessel IMO number, exactly 7 digits (e.g. 9839179). Provide exactly one of mmsi, imo, or uuid.
mmsiNoVessel MMSI identifier, exactly 9 digits (e.g. 477553000). Provide exactly one of mmsi, imo, or uuid.
uuidNoDatalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eniYes
imoYes
latYes
lonYes
mmsiYes
nameYes
typeYes
uuidYes
speedYes
courseYes
atd_UTCYes
eta_UTCYes
headingYes
dep_portYes
timezoneYes
atd_epochYes
dest_portYes
eta_epochYes
country_isoYes
destinationYes
dep_port_uuidYes
type_specificYes
dest_port_uuidYes
current_draughtYes
dep_port_unlocodeYes
last_position_UTCYes
navigation_statusYes
dest_port_unlocodeYes
last_position_epochYes
timezone_offset_secYes

TDQS

A4.7/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It notes the tool is 'heavier on the backend' and mentions staleness condition. Could explicitly state read-only nature, but overall discloses behavioral traits well.

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?

Three efficiently written sentences, front-loading purpose, then guidelines, then a behavioral note. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (multiple identifiers, enriched output, sibling tools), the description fully covers use case, return fields, and when to consider alternatives. Output schema exists but description explains return values sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% with descriptions for each parameter. Description reinforces mutual exclusivity and format constraints (9-digit MMSI, 7-digit IMO, UUID). Adds value by explaining the identification requirement beyond schema.

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?

Clearly states the tool is a richer variant of get_vessel for a single vessel, enumerating the additional fields (destination port, origin port, ATD, ETA, draught). Distinguishes from sibling get_vessel by specifying the enriched data.

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

Usage Guidelines5/5

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

Explicitly recommends get_vessel for ordinary lookups and get_vessel_pro only when specific enriched fields are needed. Also suggests estimated_vessel_position for stale positions, providing clear when-to-use and when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: vessel tracking (get_vessel, get_vessel_pro, get_vessel_history, get_vessel_info, estimated_vessel_position), registry search (find_vessels, find_ports), port details (get_port), weather (get_weather), sea route (sea_route), async reports (report_*), and intelligence modules (intel_*). Even similar tools like find_vessels vs get_vessel are well-differentiated by their descriptions.

Naming Consistency5/5

All tool names follow a consistent lowercase underscore pattern with a verb_noun structure (e.g., get_vessel, find_ports, sea_route). The intel_* tools use a uniform prefix for intelligence operations, maintaining predictability across the set.

Tool Count3/5

With 25 tools, this server is at the upper boundary of the borderline range. While the tools are well-organized and necessary for the comprehensive maritime intelligence domain, the count feels slightly heavy compared to an ideal 3-15 tool scope.

Completeness5/5

The tool surface is remarkably complete: it covers vessel tracking (live, historic, estimated), registry search, port details, weather, sea route calculation, async report management, and a full suite of intelligence reports (casualties, inspections, ownership, etc.). There are no obvious gaps for maritime vessel tracking and intelligence tasks.