Skip to main content
Glama

Coverage and sources

get_coverage
Read-onlyIdempotent

Where Open Waters AIS is hearing AIS right now: sources with their current delay, stations, freshness, and vessel counts. A bounding box adds the stations whose coverage overlaps that area and a count of vessels in it. A station ID adds statistics for that station. Vessel counts cover the last 30 minutes; max_age widens them, to 7d for the last week or all for every vessel the network has heard. An area without reports may have gaps in coverage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNoarea for station coverage and vessel counts
max_ageNocount vessels heard within this long, network-wide and in bbox, instead of the last 30 minutes: a duration such as 6h, 24h, or 7d, or all for every vessel the network has heard
stationNostation ID for station-specific statistics

Output Schema

NameRequiredDescriptionDefault
areaNo
noteNo
timeYes
sourcesYes
stationNo
summaryYes
vesselsYes
stationsYes
events_per_secondYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / bbox / description
      Previous value: -"report the stations covering this box and the vessels currently in it"New value: +"area for station coverage and vessel counts"
    • changedInput schema / properties / station / description
      Previous value: -"a station id from an earlier result, for that station's numbers"New value: +"station ID for station-specific statistics"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / area / properties / stations / items / properties / bbox / description
      Previous value: -"extent of the positions this station has heard"New value: +"extent of the positions this station has heard since the server last started; absent until it hears one"
    • changedOutput schema / properties / station / properties / bbox / description
      Previous value: -"extent of the positions this station has heard"New value: +"extent of the positions this station has heard since the server last started; absent until it hears one"
  3. Changed3 schema fields changed
    • changedOutput schema / properties / area / properties / stations / items / properties / vessels / description
      Previous value: -"distinct vessels heard in the last 30 minutes"New value: +"distinct vessels whose positions the station heard in the last 30 minutes, its own left out, up to about 7 minutes behind"
    • changedOutput schema / properties / sources / items / properties / vessels / description
      Previous value: -"distinct vessels heard from this source in the last 30 minutes"New value: +"distinct vessels whose positions this source's stations heard in the last 30 minutes, up to about 7 minutes behind"
    • changedOutput schema / properties / station / properties / vessels / description
      Previous value: -"distinct vessels heard in the last 30 minutes"New value: +"distinct vessels whose positions the station heard in the last 30 minutes, its own left out, up to about 7 minutes behind"
  4. Changed8 schema fields changed
    • addedInput schema / properties / max_age
      Added value: +{
      +  "description": "count vessels heard within this long, network-wide and in bbox, instead of the last 30 minutes: a duration such as 6h, 24h, or 7d, or all for every vessel the network has heard",
      +  "type": "string"
      +}
    • changedOutput schema / properties / area / properties / vessels / description
      Previous value: -"vessels with a position inside the box"New value: +"vessels whose last known position is inside the box, heard in the last 30 minutes or within max_age"
    • addedOutput schema / properties / vessels / properties / active
      Added value: +{
      +  "description": "vessels heard in the last 30 minutes",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / vessels / properties / heard
      Added value: +{
      +  "description": "vessels heard within max_age; present when max_age is given",
      +  "type": [
      +    "null",
      +    "integer"
      +  ]
      +}
    • addedOutput schema / properties / vessels / properties / new
      Added value: +{
      +  "description": "vessels first heard within max_age; present when max_age is a duration",
      +  "type": [
      +    "null",
      +    "integer"
      +  ]
      +}
    • changedOutput schema / properties / vessels / properties / total / description
      Previous value: -"vessels heard in the last 30 minutes"New value: +"every vessel the network has heard"
    • addedOutput schema / properties / vessels / properties / with_position / description
      Added value: +"of the active vessels, those with a position"
    • changedOutput schema / properties / vessels / required
      Previous value: -[
      -  "total",
      -  "with_position"
      -]New value: +[
      +  "total",
      +  "active",
      +  "with_position"
      +]
  5. Changed1 schema field changed
    • addedOutput schema / properties / sources / items / properties / delay
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "seconds from broadcast to arrival over the last position reports from this source",
      +  "properties": {
      +    "p50": {
      +      "description": "median delay in seconds",
      +      "type": "number"
      +    },
      +    "p99": {
      +      "description": "99th percentile delay in seconds",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "p50",
      +    "p99"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, so the description is free to add the details that matter: counts default to the last 30 minutes, max_age widens that window, and empty areas may reflect coverage gaps rather than absence of vessels. Missing is any note on latency/rate limits when querying sources, but the substantive behavioral context is present.

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?

Purpose is front-loaded in the first sentence, followed by one sentence per parameter mode and a closing caveat. Dense but nearly every clause carries information; the '7d for the last week' illustration is mildly redundant with the duration examples but harmless.

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?

With zero required parameters, an output schema present, and full schema coverage, this description covers the remaining burden well: what data is returned, how each optional filter changes scope, the default time window, and the interpretation caveat for empty areas. Nothing needed to invoke it correctly is absent.

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 each parameter is already documented; the description still adds cross-parameter meaning — bbox yields both overlapping stations and a vessel count, station yields station statistics, and max_age changes the counting window network-wide as well as inside the bbox. This goes beyond restating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: network coverage status — sources, delay, stations, freshness and vessel counts. That clearly separates it from vessel-lookup siblings, but it never explicitly says it is not the tool for listing vessels in an area, which find_vessels_in_area also promises.

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

Usage Guidelines3/5

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

Explains what each optional parameter adds ('A bounding box adds...', 'A station ID adds...'), which implies the three usage modes, and warns that 'An area without reports may have gaps in coverage.' There is no explicit when-to-use-vs-alternative guidance against sibling tools that also count vessels in an area.

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.