Skip to main content
Glama
vessel-api

VesselAPI MCP Server

by vessel-api
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript

search_vessels

Search for vessels by name, IMO, MMSI, ENI, or callsign, and filter by flag, type, and year built to locate specific ships or narrow a fleet.

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.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. 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"
+}
  2. Addedv1.3.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose pagination behavior, return format, or any side effects. It only explains search semantics; for a read-only search this is minimal, but safety implications are left unstated.

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?

The description is two sentences with clear front-loading: 'Search for vessels.' followed by targeted usage guidance. Every word earns its place.

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?

The tool has many optional parameters and no output schema. The description is brief but the schema covers parameter details. Missing info on pagination or response structure, though limit/nextToken are in schema. It orients the user but is not fully complete.

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?

The schema provides 100% coverage of all 12 parameters with descriptions, so the baseline is 3. The description adds strategic semantics about q for unknown identifiers and specific filters for narrowing a fleet, adding value beyond the 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 clearly states the action: 'Search for vessels.' It also distinguishes between using 'q' for unknown identifiers and specific filters for narrowing a fleet, which helps differentiate from sibling get_vessel* tools that fetch by known IDs.

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?

Provides explicit usage guidance: use 'q' when the identifier type is unknown, and use specific filters to narrow a fleet. However, it does not mention alternatives like get_vessel for known IDs or compare with other sibling search tools, so it's clear but not exhaustive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vessel-api/vesselapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server