Skip to main content
Glama

Datalastic Vessel Tracking & Maritime Intelligence

by com.datalastic

Get vessels in radius (area scan)

get_vessels_in_radius

Scan a circular area and return all vessels currently within a given radius (nautical miles, greater than 0 and at most 50). Specify the center in exactly one way: lat+lon coordinates, a port (port_unlocode or port_uuid), or a vessel to center on (mmsi/imo/uuid). Optional filters: type, type_specific, exclude, nav_status, and include_unknown_type. Returns up to 500 vessels per page, each with its distance (nautical miles) from the center; if more remain, pass the response's 'next' token via the 'next' argument to page through them. Credits are charged per vessel found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imoNoCenter the scan on a vessel, by IMO (exactly 7 digits).
latNoCenter latitude (-90..90). Must be used together with lon. Provide exactly one center: lat+lon, a port, or a vessel identifier.
lonNoCenter longitude (-180..180). Must be used together with lat.
mmsiNoCenter the scan on a vessel, by MMSI (exactly 9 digits).
nextNoOptional: pagination token from a previous response's 'next' field, to fetch the next page (up to 500 vessels per page).
typeNoOptional: only include vessels of this type (e.g. Tanker, Cargo).
uuidNoCenter the scan on a vessel, by Datalastic vessel UUID.
radiusYesRequired. Scan radius in nautical miles, greater than 0 and at most 50.
excludeNoOptional: exclude vessels of this type.
port_uuidNoCenter the scan on a port, by Datalastic port UUID.
nav_statusNoOptional: filter by AIS navigational status number (e.g. 0 = under way using engine).
port_unlocodeNoCenter the scan on a port, by UN/LOCODE (e.g. ESVLC).
type_specificNoOptional: only include vessels of this specific subtype (e.g. LPG Tanker).
include_unknown_typeNoOptional: include vessels that have no/unknown type. Defaults to the API default when omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextYes
pointYes
totalYes
vesselsYes

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: charges credits per vessel found, returns up to 500 per page, pagination via 'next' token, and enforces exclusive center specification. It lacks details on rate limits or authentication, but for a read-only scan, it is 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?

The description is very concise while covering all essential aspects. It uses front-loaded sentences and a clear structure, with no wasted words. Every sentence adds necessary information.

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 14 parameters, 100% schema coverage, and existence of an output schema, the description is complete. It covers the core operation, center specification options, filters, pagination, and cost implications, leaving no major gaps.

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%, so baseline is 3. The description adds meaningful context beyond the schema: explains scan concept, center exclusivity, pagination output structure, and credit charging. It helps agents understand parameter purpose beyond type/constraint.

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's purpose: scan a circular area and return all vessels within a given radius. It uses specific verbs (scan, return) and resource (vessels), distinguishing it from siblings like get_vessel (single vessel) or find_vessels (search by name).

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

Usage Guidelines4/5

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

The description provides explicit instructions on when to use the tool (area scan) and how to specify the center (lat+lon, port, or vessel). It also explains optional filters and pagination. However, it does not explicitly mention when not to use it or compare to alternatives, though the context is clear.

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 toolsInspect
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.

Resources