Skip to main content
Glama
vessel-api

VesselAPI MCP Server

by vessel-api
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_vessels_in_area

Find vessels located within a specified latitude/longitude bounding box. Filter results by time window and paginate through up to 50 results per page.

Instructions

Find all vessels within a rectangular bounding box (latitude/longitude)

Input Schema

TableJSON 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. 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."
  2. Addedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, and the description implies a read-only operation ('Find') without explicitly stating side effects, permissions, or return values. While it likely does not modify data, the lack of clarity about outputs or potential restrictions limits transparency.

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?

The description is a single concise sentence that accurately summarizes the tool's primary function without redundancy. It omits details that are appropriately captured in the schema, maintaining a clean and focused structure.

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

Completeness3/5

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

While the description and schema cover the inputs well, the tool lacks an output schema, and the description does not specify what the response contains (e.g., vessel IDs, full details). The presence of pagination and time window parameters suggests additional context, but the lack of response documentation reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are listed and described in the schema, including their purpose and constraints (e.g., limit has maximum 50, time window limits). The bounding box and pagination fields are clearly explained, and the required parameters are self-evident. This provides excellent parameter clarity.

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 tool name 'get_vessels_in_area' and description unambiguously specify the operation: retrieving vessels within a rectangular bounding box defined by latitude/longitude. The description is concise and direct, making the purpose immediately clear.

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?

The description explains what the tool does but does not explicitly state when to use it relative to other similar tools like 'get_vessels_in_radius' or 'search_vessels'. It also does not mention prerequisites or typical use cases, leaving some ambiguity for a user choosing between sibling tools.

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

Deploy Server

Other Tools