mcp

Find a port / UN/LOCODE (no key)

find_port

Read-onlyIdempotent

Resolve a port name, country or partial UN/LOCODE to the LOCODEs the routing engine knows. Routes are addressed by LOCODE, so call this before score_voyage rather than guessing a code. Works with no API key.

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": {
      "query": "<query>"
    },
    "name": "find_port"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum matches to return (default 5)
`query`	Yes	Port name, country, or LOCODE fragment, e.g. "rotterdam", "NLRTM", "Piraeus"

Output Schema

Name	Required	Description	Default
`ports`	Yes	Best matches first

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "ports": {
+      "description": "Best matches first",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "country": {
+            "type": "string"
+          },
+          "locode": {
+            "description": "UN/LOCODE, e.g. NLRTM",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "locode",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ports"
+  ],
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds context beyond annotations: it explains the tool resolves to known LOCODEs, that routes are addressed by LOCODE, and that no API key is needed. It doesn't describe output format, but the output schema exists, so that burden is reduced.

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?

Three sentences with no waste. The core purpose is front-loaded, the usage directive is clear, and the no-key note is a valuable addition. Every sentence earns its place.

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 simple lookup tool with 2 params, full schema coverage, and an output schema, the description is nearly complete. It explains why to use it (LOCODE addressing), when to use it (before score_voyage), and the no-key requirement. The only minor gap is not describing what the response contains, but the output schema covers that.

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 both parameters (query and limit) with examples. The description adds the context that query can be a port name, country, or LOCODE fragment, which reinforces but doesn't significantly extend the schema. Baseline 3 is appropriate.

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 states a specific verb ('Resolve') and resource ('port name, country or partial UN/LOCODE to the LOCODEs the routing engine knows'), and explicitly distinguishes itself from score_voyage by explaining that routes are addressed by LOCODE. This clearly differentiates it from siblings like check_vessel and screen_vessel.

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

Usage Guidelines5/5

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

The description explicitly says to call this before score_voyage rather than guessing a code, providing a clear when-to-use directive. It also notes that it works with no API key, which is a useful prerequisite clarification. This is strong usage guidance.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.