Skip to main content
Glama

Where a vessel has been

get_vessel_track
Read-onlyIdempotent

The positions heard from one vessel over a time range, oldest first, with speed, course, and navigational status. Positions implying an impossible speed for the vessel are left out. A vessel can be identified by MMSI, or by IMO with a feeder or partner token. A call covers up to a year. By default the track is simplified by shape: the positions that hold its path, with breaks where the vessel went unheard; interval_minutes asks for even spacing instead.

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_vessel_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoend, RFC 3339 UTC; default now
imoNothe vessel's IMO number, instead of mmsi; needs a feeder or partner token. Follows the one vessel the IMO names: its only MMSI, or the only one heard in the last 30 days
fromNostart, RFC 3339 UTC; default 24 hours before to. A call covers up to 366 days
mmsiNothe vessel's MMSI, as an alternative to its IMO number
limitNopositions to return: default 50, maximum 200; when more match, the newest are kept
interval_minutesNoat most one position per this many minutes, evenly spaced; by default the track is simplified by shape instead, keeping the positions that hold its path. Anonymous and personal calls reaching past 48 hours are rounded up to whole minutes

Output Schema

NameRequiredDescriptionDefault
toYes
fromYesstart of the range covered
mmsiYes
nameNo
breaksNosimplified, always present and empty when the vessel was heard throughout: indexes of positions that start a new segment after a gap in reports
positionsYesoldest first
truncatedYestrue when positions were left out: simplified, the tolerance rose past 15 m to fit the limit, or the range held more than 50,000 positions and the oldest were not read; by interval, the newest were kept
interval_sYesat most one position per this many seconds; 0 is every position heard. Simplified, the resolution the positions were read at
simplifiedYestrue when the track was simplified by shape: the positions that hold its path, not evenly spaced
attributionYesattribution required when displaying the positions, by source kind
tolerance_mNosimplified: every position left out lay within this many meters of the line through the ones kept

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / mmsi / description
      Previous value: -"the vessel's MMSI; give mmsi or imo. Use search_vessels_by_name first when you only have a name"New value: +"the vessel's MMSI, as an alternative to its IMO number"
    • changedOutput schema / properties / attribution / description
      Previous value: -"credit line per source kind in the positions, to show with the data"New value: +"attribution required when displaying the positions, by source kind"
    • changedOutput schema / properties / breaks / description
      Previous value: -"simplified, always present and empty when the vessel was heard throughout: indexes of positions that start a stretch after it went unheard; draw no line into them"New value: +"simplified, always present and empty when the vessel was heard throughout: indexes of positions that start a new segment after a gap in reports"
    • changedOutput schema / properties / truncated / description
      Previous value: -"true when positions were left out: simplified, the tolerance rose past 15 m to fit the limit, or the range held more than 50,000 positions and the oldest were not read; by interval, the newest were kept, so set from later or raise interval_minutes"New value: +"true when positions were left out: simplified, the tolerance rose past 15 m to fit the limit, or the range held more than 50,000 positions and the oldest were not read; by interval, the newest were kept"
  2. Changed3 schema fields changed
    • addedInput schema / properties / imo
      Added value: +{
      +  "description": "the vessel's IMO number, instead of mmsi; needs a feeder or partner token. Follows the one vessel the IMO names: its only MMSI, or the only one heard in the last 30 days",
      +  "maximum": 4294967295,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / mmsi / description
      Previous value: -"the vessel's MMSI; use search_vessels_by_name first when you only have a name"New value: +"the vessel's MMSI; give mmsi or imo. Use search_vessels_by_name first when you only have a name"
    • removedInput schema / required
      Removed value: -[
      -  "mmsi"
      -]
  3. Changed7 schema fields changed
    • changedInput schema / properties / interval_minutes / description
      Previous value: -"at most one position per this many minutes; by default the limit is spread over the range at a round spacing, reported as interval_s. Anonymous and personal calls reaching past 48 hours are rounded up to whole minutes"New value: +"at most one position per this many minutes, evenly spaced; by default the track is simplified by shape instead, keeping the positions that hold its path. Anonymous and personal calls reaching past 48 hours are rounded up to whole minutes"
    • addedOutput schema / properties / breaks
      Added value: +{
      +  "description": "simplified, always present and empty when the vessel was heard throughout: indexes of positions that start a stretch after it went unheard; draw no line into them",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • changedOutput schema / properties / interval_s / description
      Previous value: -"at most one position per this many seconds; 0 is every position heard"New value: +"at most one position per this many seconds; 0 is every position heard. Simplified, the resolution the positions were read at"
    • addedOutput schema / properties / simplified
      Added value: +{
      +  "description": "true when the track was simplified by shape: the positions that hold its path, not evenly spaced",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / tolerance_m
      Added value: +{
      +  "description": "simplified: every position left out lay within this many meters of the line through the ones kept",
      +  "type": [
      +    "null",
      +    "number"
      +  ]
      +}
    • changedOutput schema / properties / truncated / description
      Previous value: -"true when more positions matched than were returned; the newest were kept, so set from later or raise interval_minutes"New value: +"true when positions were left out: simplified, the tolerance rose past 15 m to fit the limit, or the range held more than 50,000 positions and the oldest were not read; by interval, the newest were kept, so set from later or raise interval_minutes"
    • changedOutput schema / required
      Previous value: -[
      -  "mmsi",
      -  "from",
      -  "to",
      -  "interval_s",
      -  "positions",
      -  "truncated",
      -  "attribution"
      -]New value: +[
      +  "mmsi",
      +  "from",
      +  "to",
      +  "interval_s",
      +  "simplified",
      +  "positions",
      +  "truncated",
      +  "attribution"
      +]
  4. Changed3 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"start, RFC 3339 UTC; default 24 hours before to. Anonymous and personal calls reach back 48 hours; feeder and commercial tokens reach the archive, up to 366 days per call"New value: +"start, RFC 3339 UTC; default 24 hours before to. A call covers up to 366 days"
    • changedInput schema / properties / interval_minutes / description
      Previous value: -"at most one position per this many minutes; by default the limit is spread over the range at a round spacing, reported as interval_s"New value: +"at most one position per this many minutes; by default the limit is spread over the range at a round spacing, reported as interval_s. Anonymous and personal calls reaching past 48 hours are rounded up to whole minutes"
    • changedOutput schema / properties / from / description
      Previous value: -"start of the range covered, after clamping to what the caller can reach: the last 48 hours, or the archive for feeder and commercial tokens"New value: +"start of the range covered"
  5. Changed1 schema field changed
    • changedInput schema / properties / from / description
      Previous value: -"start, RFC 3339 UTC; default 24 hours before to. Anonymous and personal calls reach back 48 hours; feeder and commercial tokens reach the archive, up to 7 days per call"New value: +"start, RFC 3339 UTC; default 24 hours before to. Anonymous and personal calls reach back 48 hours; feeder and commercial tokens reach the archive, up to 366 days per call"
  6. Changed5 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"start, RFC 3339 UTC; default 24 hours before to. Positions reach back 48 hours"New value: +"start, RFC 3339 UTC; default 24 hours before to. Anonymous and personal calls reach back 48 hours; feeder and commercial tokens reach the archive, up to 7 days per call"
    • changedInput schema / properties / interval_minutes / description
      Previous value: -"at most one position per this many minutes; by default the positions are spread evenly over the range"New value: +"at most one position per this many minutes; by default the limit is spread over the range at a round spacing, reported as interval_s"
    • changedOutput schema / properties / from / description
      Previous value: -"start of the range covered, after clamping to the last 48 hours"New value: +"start of the range covered, after clamping to what the caller can reach: the last 48 hours, or the archive for feeder and commercial tokens"
    • addedOutput schema / properties / interval_s
      Added value: +{
      +  "description": "at most one position per this many seconds; 0 is every position heard",
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "mmsi",
      -  "from",
      -  "to",
      -  "positions",
      -  "truncated",
      -  "attribution"
      -]New value: +[
      +  "mmsi",
      +  "from",
      +  "to",
      +  "interval_s",
      +  "positions",
      +  "truncated",
      +  "attribution"
      +]
  7. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses ordering (oldest first), filtering of impossible-speed positions, the year-long call cap, shape-based simplification with breaks where the vessel went unheard, and the token requirement for IMO lookup. These are meaningful behavioral details an agent could not infer from annotations alone.

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?

Four dense sentences are front-loaded with the core return behavior, then identification, time range, and simplification mode. The wording is efficient, though the final sentence is long and combines several related constraints.

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 annotations covering safety, an output schema covering return values, and full schema parameter descriptions, the description supplies the remaining operational context needed to call the tool correctly. Nothing material appears missing.

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 description coverage is 100%, so the schema already documents time defaults, limits, identification modes, and interval behavior. The description reinforces the default shape-simplification mode and the interval alternative, but adds little parameter meaning beyond the structured schema.

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 gives a specific verb-and-resource action: it returns the positions heard from one vessel over a time range, with speed, course, and navigational status. This clearly distinguishes it from sibling tools that list, find, or search vessels by identity or location.

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?

It explains vessel identification via MMSI or IMO with a feeder/partner token, the default and maximum time ranges, and when to request even spacing with interval_minutes instead of shape simplification. It does not explicitly contrast itself with the find_* or get_vessels siblings, but the usage context is clear.

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.