Skip to main content
Glama
VesselAPI MCP Server

VesselAPI MCP Server

get_vessels_in_area

Finds vessels with AIS positions within a rectangular bounding box and time window to support maritime area monitoring.

Instructions

Find vessels with an AIS position inside a rectangular bounding box during the time window (default the last 2 hours, at most 4 hours). The latitude span plus the longitude span may not exceed 4 degrees.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latMin": "<latMin>",
      "latMax": "<latMax>",
      "lonMin": "<lonMin>",
      "lonMax": "<lonMax>"
    },
    "name": "get_vessels_in_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, 1 to 50. Defaults to 20.
latMaxYesNorthern boundary latitude
latMinYesSouthern boundary latitude
lonMaxYesEastern boundary longitude
lonMinYesWestern boundary longitude
timeToNoEnd of the time window, RFC3339. Defaults to now. The window may not exceed 4 hours.
timeFromNoStart of the time window, RFC3339. Defaults to 2 hours ago. The window may not exceed 4 hours.
nextTokenNoPagination token from previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed6 schema fields changedv2.0.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per page"New value: +"Results per page, 1 to 50. Defaults to 20."
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / timeFrom / description
      Previous value: -"Start time filter in RFC3339 format (defaults to 2 hours ago)"New value: +"Start of the time window, RFC3339. Defaults to 2 hours ago. The window may not exceed 4 hours."
    • changedInput schema / properties / timeTo / description
      Previous value: -"End time filter in RFC3339 format (defaults to current time)"New value: +"End of the time window, RFC3339. Defaults to now. The window may not exceed 4 hours."
  3. Addedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden, and it does disclose the time-window limits and the 4-degree span cap (the latter not in the schema). It does not say what a result contains (vessel identity, latest position, timestamp), whether results are deduplicated, or how pagination terminates.

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?

Two sentences, both load-bearing, with the core operation front-loaded and the geometric constraint following. Nothing is repeated from the title or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, no-annotation, no-output-schema query tool, the description covers the geometry, the time window, and both hard limits. The remaining gap is return-value shape and pagination semantics, which the schema's nextToken field only partially covers.

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 the baseline is 3, but the description adds a real cross-parameter constraint the schema never states: the combined latitude and longitude span may not exceed 4 degrees. That meaningfully informs how latMin/latMax/lonMin/lonMax must be chosen together.

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?

The description names a specific verb ('Find') and resource ('vessels with an AIS position') and scopes it to a rectangular bounding box plus a time window. The 'rectangular bounding box' framing implicitly contrasts with the sibling get_vessels_in_radius, but it never names that alternative explicitly.

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?

It states the default window (last 2 hours) and the hard cap (at most 4 hours), which is genuine usage context. It gives no guidance on when to prefer this over get_vessels_in_radius, get_vessel_position, or get_vessel_positions_batch, and no exclusions or prerequisites.

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