Skip to main content
Glama

Live Ships In Area

live_ships_in_area
Read-onlyIdempotent

Live ship positions right now in a geographic area, from AIS radio broadcasts — what vessels are sailing near a port, coastline, strait or set of coordinates at this moment. Returns each vessel heard with its position, speed, course, navigational status, type, destination and IMO where broadcast, plus a breakdown by vessel type (cargo, tanker, passenger, fishing, tug). Give either a centre point (latitude + longitude + radius_km) or a bounding box. COVERAGE IS PARTIAL AND TERRESTRIAL — there is no receiver coverage in the Persian Gulf, Strait of Hormuz, Gulf of Oman or Red Sea, so this tool cannot answer questions about those waters (use chokepoint_status for Hormuz/Suez/Bab el-Mandeb transit counts instead). Counts are vessels heard during a listening window of a few seconds, not a complete count of vessels present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eastNoBounding box eastern longitude
westNoBounding box western longitude
limitNoMaximum vessels to return (default 50, max 300)
northNoBounding box northern latitude
southNoBounding box southern latitude (alternative to centre+radius)
_apiKeyNoaisstream.io API key (free at aisstream.io)
latitudeNoCentre latitude, e.g. 43.3 for Marseille
longitudeNoCentre longitude, e.g. 5.4 for Marseille
radius_kmNoRadius around the centre point in km (default 50, max 500)
ship_typeNoOptional filter on decoded type, e.g. "tanker", "cargo", "passenger", "fishing", "tug"
window_secondsNoHow long to listen, 3-25 seconds (default 12). Longer windows hear more vessels, especially anchored ones which only transmit every ~3 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Description adds substantial behavioral context beyond the annotations: partial terrestrial coverage, specific exclusions (Persian Gulf/Hormuz/Red Sea), the listening-window nature of counts, and the fact that returns are only vessels heard, not a complete census. No contradiction with annotations.

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 dense and front-loaded with the core purpose, then covers usage modes, coverage limitations, and return payload. Every sentence contributes unique information; no filler or redundancy. Well-structured for a complex 11-parameter tool.

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 lack of an output schema, the description fully describes the return value (vessel fields plus type breakdown) and important caveats (partial coverage, non-complete counts). It also names an alternative tool for excluded regions, making it complete for operational use.

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 covers 100% of parameters, so baseline is 3. The description adds meaningful semantic context: explains the centre-vs-bounding-box alternatives, and clarifies that window_seconds affects the ability to hear anchored vessels. It does not restate every schema description, but adds value.

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 function: live AIS-derived ship positions for a geographic area. It specifies the resource (ships in an area) and the verb (live positions), and distinguishes itself from sibling tools like live_ship_position (single ship) and ais_coverage_check.

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?

Usage guidance is explicit: provides both centre+radius and bounding box options, and gives an alternative tool (chokepoint_status) for areas without coverage. It also explains when to use (near ports/coastlines/coordinates) and notes coverage exclusions.

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.