Skip to main content
Glama
Sign In
VesselAPI MCP Server

VesselAPI MCP Server

by vessel-api
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_port

Retrieve detailed port information by UN/LOCODE to support maritime routing, logistics, and vessel operations planning.

Instructions

Get detailed information about a specific port by UN/LOCODE

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": {
      "unlocode": "<unlocode>"
    },
    "name": "get_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
unlocodeYesUN/LOCODE of the port (e.g. NLRTM for Rotterdam)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.3.0

TDQS

B3.3/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 lookup but does not state what happens with invalid codes, what 'detailed information' includes, or any permission or error behavior.

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 a single, front-loaded sentence with no filler or redundancy. Every word contributes to identifying the operation.

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 simple one-parameter lookup this is minimally adequate, but with no output schema and no annotations, the description could do more to set expectations about the returned port details or failure cases. It is sufficient to attempt the call but leaves clear gaps.

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 sole unlocode parameter is already documented with an example in the schema. The description adds no parameter detail beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: getting detailed information about a specific port, keyed by UN/LOCODE. It clearly identifies the lookup operation, though it does not explicitly distinguish itself from siblings such as search_ports or get_port_inbound.

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 phrase 'by UN/LOCODE' implies the tool should be used when the caller already has a port code, but there is no explicit guidance on when to prefer search_ports or other port-related siblings. Usage is inferable but not fully specified.

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