Skip to main content
Glama
VesselAPI MCP Server

VesselAPI MCP Server

search_vessels

Find vessels by name, IMO, MMSI, ENI, callsign, flag, type, or build year; use free-text search when the identifier type is unknown, then narrow results with filters.

Instructions

Search for vessels. Use q when you have an identifier but do not know which kind it is; use the specific filters to narrow a fleet.

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": "search_vessels"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search across name, IMO, MMSI, ENI and callsign. Use this when the type of identifier is unknown.
eniNoENI number, used for inland waterway vessels
imoNoIMO number
flagNoFlag state (ISO country code)
mmsiNoMMSI number
nameNoVessel name (partial match)
limitNoResults per page, 1 to 50. Defaults to 20.
callsignNoRadio callsign
nextTokenNoPagination token from previous response
vesselTypeNoVessel type
yearBuiltMaxNoMaximum year built
yearBuiltMinNoMinimum year built

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed8 schema fields changedv2.0.0
    • removedInput schema / properties / classSociety
      Removed value: -{
      -  "description": "Classification society (case-insensitive)",
      -  "type": "string"
      -}
    • addedInput schema / properties / eni
      Added value: +{
      +  "description": "ENI number, used for inland waterway vessels",
      +  "type": "string"
      +}
    • 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"
    • removedInput schema / properties / owner
      Removed value: -{
      -  "description": "Owner name (partial match, case-insensitive)",
      -  "type": "string"
      -}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Free-text search across name, IMO, MMSI, ENI and callsign. Use this when the type of identifier is unknown.",
      +  "type": "string"
      +}
  3. Addedv1.3.0

TDQS

A3.5/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. It implies a read-only search but does not state side effects, auth requirements, result shape, sorting, or pagination behavior beyond what the schema fields already say.

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, front-loaded with purpose and followed by practical selection guidance. There is no wasted text.

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?

For a 12-parameter search tool with no annotations and no output schema, the description is thin. Parameter definitions cover the inputs, but return values, pagination expectations, and result ordering are not described.

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 all 12 parameters. The description adds only a high-level q-vs-filter selection rule and does not add syntax, matching semantics, or filter-combination details beyond 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 verb and resource: 'Search for vessels.' It is clear what the tool does, but it does not differentiate this general search from sibling tools such as get_vesssel, get_vessels_in_area, or get_vessels_in_radius beyond the q-vs-filters hint.

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?

The description gives clear context for choosing q when the identifier type is unknown and for using specific filters to narrow a fleet. It does not explicitly exclude use cases or name alternative tools for other modes of lookup.

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