Skip to main content
Glama
VesselAPI MCP Server

VesselAPI MCP Server

get_vessel

Retrieve detailed information about a specific vessel using its IMO or MMSI identifier to support maritime tracking and safety analysis.

Instructions

Get detailed information about a specific vessel

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": {
      "vesselId": "<vesselId>"
    },
    "name": "get_vessel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idTypeNoIdentifier type: imo (default) or mmsi
vesselIdYesVessel identifier (IMO number by default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / idType / description
      Previous value: -"Identifier type: imo (default), mmsi, or vesselId"New value: +"Identifier type: imo (default) or mmsi"
    • addedInput schema / properties / idType / enum
      Added value: +[
      +  "imo",
      +  "mmsi"
      +]
  3. Addedv1.3.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost nothing: no indication of what 'detailed information' contains, whether the call is cached or rate-limited, or what happens for an unknown or ambiguous identifier. Only the read-only nature can be inferred from the verb 'Get'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero waste and the resource front-loaded, but its brevity reflects under-specification rather than disciplined concision; it could afford one more clause naming the returned detail scope.

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

Completeness2/5

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

The tool is simple (2 params, 1 required, no output schema, no annotations), which lowers the bar, but an agent still cannot tell from this description what makes it distinct from the many other vessel-detail endpoints or what to expect back. Without an output schema the description should at least sketch the returned fields.

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 coverage is 100% — the schema itself documents vesselId (IMO by default) and the idType enum of imo/mmsi. The description adds no format, validation, or default details beyond that, so the baseline 3 applies.

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 clear verb and resource: 'Get detailed information about a specific vessel.' An agent can tell it retrieves a single vessel by identifier, but the description never differentiates it from siblings such as get_vessel_position, get_vessel_eta, get_vessel_emissions, or search_vessels, so the scope of 'detailed information' stays ambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternatives. The word 'specific' only faintly implies that the caller must already hold an identifier rather than search, which is too weak a signal next to ten-plus vessel-related siblings.

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