Skip to main content
Glama

Vesselfinder Vessel

vesselfinder_vessel
Read-onlyIdempotent

Where is ship <imo/mmsi>, live AIS position, destination, ETA, and particulars. Returns the latest reported position (lat/lon, course, speed, heading, nav status), voyage info (destination, ETA, draught), and vessel particulars (type, flag, gross tonnage, deadweight). Provide either an IMO or an MMSI number. Example: vesselfinder_vessel({ imo: "9074729", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "imo": "9074729",
      "_apiKey": "your-vesselfinder-api-key"
    },
    "name": "vesselfinder_vessel"
  }
}

Input Schema

NameRequiredDescriptionDefault
imoNoIMO number of the vessel, e.g. "9074729". Provide imo or mmsi.
mmsiNoMMSI number of the vessel, e.g. "477553000". Provide imo or mmsi.
_apiKeyYesVesselFinder API key (prepaid credits, get one at vesselfinder.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"VesselFinder API key (prepaid credits — get one at vesselfinder.com)"New value: +"VesselFinder API key (prepaid credits, get one at vesselfinder.com)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: it spells out the returned payload (position, course, speed, nav status, ETA, draught, tonnage) in the absence of an output schema, and signals that the data is the "latest reported" position rather than a live stream. It stops short of noting credit consumption or behavior when a vessel is not found.

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?

Front-loaded with the core question ("Where is ship"), followed by return contents, then the parameter rule. Every sentence carries information, though the trailing example duplicates the examples already present in the input schema and could be dropped without loss.

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 a three-parameter read-only lookup with no output schema, the description covers purpose, returned fields, and identifier requirements adequately. Remaining gaps are minor but real: no statement about credit cost per call, data staleness, or the response when an identifier resolves to nothing.

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%, and the schema already states "Provide imo or mmsi" for both identifier fields and explains the API key. The description repeats the either/or rule and adds an example call, but contributes no new meaning such as whether IMO is preferred when both are supplied or what format validation applies.

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?

"Where is ship <imo/mmsi>, live AIS position, destination, ETA, and particulars" names a specific verb (look up) and resource (vessel) and enumerates the returned fields. No sibling tool in the catalog does vessel lookups, so the tool is unambiguously distinguishable.

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 implies the usage context (retrieving live position/voyage data for a specific vessel) and tells the caller to supply either IMO or MMSI, which is the key invocation decision. It gives no explicit when-not guidance, no note on alternatives, and no mention that a lookup consumes prepaid API credits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.