Datalastic Vessel Tracking & Maritime Intelligence

Get vessel specifications

get_vessel_info

Return static specifications for a single vessel, identified by exactly one of: MMSI (9 digits), IMO (7 digits), or Datalastic UUID. Includes physical dimensions (length, breadth, draught), tonnage and cargo capacity (gross tonnage, deadweight, TEU, liquid gas), speed characteristics, year built, flag country, callsign and home port. This is reference data, NOT live position — use get_vessel for the current position, or find_vessels to search the registry by attributes.

Input Schema

TableJSON Schema

Name	Required	Description
`imo`	No	Vessel IMO number, exactly 7 digits (e.g. 9525338). Provide exactly one of mmsi, imo, or uuid.
`mmsi`	No	Vessel MMSI identifier, exactly 9 digits (e.g. 566093000). Provide exactly one of mmsi, imo, or uuid.
`uuid`	No	Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`eni`	Yes
`imo`	Yes
`teu`	Yes
`mmsi`	Yes
`name`	Yes
`type`	Yes
`uuid`	Yes
`length`	Yes
`breadth`	Yes
`callsign`	Yes
`name_ais`	Yes
`home_port`	Yes
`is_navaid`	Yes
`speed_avg`	Yes
`speed_max`	Yes
`deadweight`	Yes
`liquid_gas`	Yes
`year_built`	Yes
`country_iso`	Yes
`draught_avg`	Yes
`draught_max`	Yes
`country_name`	Yes
`gross_tonnage`	Yes
`type_specific`	Yes

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 discloses that the tool returns static reference data, not live positions, and lists the types of fields returned. It does not describe error behavior for missing identifiers or multiple identifiers, but given the read-only nature, this is mostly sufficient.

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 sentences: first states purpose and identification requirement, second lists returned fields, third clarifies not live position. No redundant information, well front-loaded, every sentence earned.

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 tool's simplicity (3 params, output schema present), the description explains how to identify the vessel, what data is returned, and how it differs from siblings. No gaps remain for an agent to misuse this tool.

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 is 100% with descriptions for each parameter. The description adds value by clarifying mutual exclusivity ('exactly one of') and providing digit count examples, which aids correct invocation beyond schema basics.

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 returns static specifications for a single vessel, using verb 'Return' and resource 'static specifications'. It explicitly distinguishes from siblings by mentioning get_vessel for live position and find_vessels for registry search.

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?

The description provides explicit when-not guidance: 'This is reference data, NOT live position — use get_vessel for the current position, or find_vessels to search the registry by attributes.' It also states the identification requirement: 'identified by exactly one of: MMSI, IMO, or Datalastic UUID.'

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

All Datalastic Vessel Tracking & Maritime Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.

Get vessel specifications

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources