Skip to main content
Glama

Datalastic Vessel Tracking & Maritime Intelligence

Estimate a vessel's current position (SAT-E)

estimated_vessel_position

Estimate where a vessel is right now when its last AIS position is stale — Datalastic uses terrestrial AIS only, so a ship in open ocean can be many hours old. The position is calculated from the last known fix, the recognized destination port, and the route-based ETA. It is an ESTIMATE, not an observed position.

Tool selection — use this LAST: prefer get_vessel for a live position (cheapest); prefer get_vessel_pro when the user wants the ETA or recognized destination. Only reach for this tool when BOTH hold: (1) a prior get_vessel/get_vessel_pro lookup shows the last known position is old, and (2) the vessel has a destination and an ETA. It is the heaviest call (it builds a route) and adds nothing when get_vessel already returns a recent position.

Because it is an estimate, OFFER it to the user first rather than calling it silently, and when you present the result make clear it is an estimated position, not a real fix. If estimated_position equals the last known lat/lon, the system could not extrapolate (the position is recent, or the ETA is missing/outdated) — say so instead of implying movement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imoNoVessel IMO number, exactly 7 digits. Provide exactly one of mmsi, imo, or uuid.
mmsiNoVessel MMSI identifier, exactly 9 digits. 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
estimated_positionYes
last_position_epochYes
timezone_offset_secYes

TDQS

A4.6/5.0
Behavior5/5

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

No annotations, but description discloses it's an estimate, explains calculation method, and warns when extrapolation fails. Full transparency on behavioral traits.

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?

Well-structured with purpose first, then usage, then behavioral notes. Dense with useful info but slightly lengthy.

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?

Output schema exists, so return values not needed. Covers use case, alternatives, error cases, and user presentation. Very complete.

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 coverage is 100% with clear descriptions of each parameter. Description does not add new parameter info but baseline is appropriate for high coverage.

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 clearly states the tool estimates a vessel's current position when last AIS is stale, distinguishing it from siblings like get_vessel (live position) and get_vessel_pro (ETA/destination).

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 advises to use this LAST after get_vessel and get_vessel_pro, only when both conditions hold, and suggests offering to user first. Also provides guidance on interpreting the result.

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.