Skip to main content
Glama

Triplicate – export documents

Look up UN/LOCODE port codes

lookup_port_code
Read-only

Use when a user needs the UN/LOCODE (port code or location code, e.g. Busan = KRPUS) of a port, airport or inland depot for a booking, bill of lading or invoice, or wants to check a code they were given. Find the 5-character UN/LOCODE of a seaport, airport or inland container depot by place name (or check a code): returns code, name, country, subdivision, type and Triplicate's country page, for the port of loading or discharge on bookings, bills of lading and invoices. UN/LOCODE 2025-1, 37,000+ places.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOptional: only seaports, airports or inland container depots
limitNo
queryYesPort, city or airport name in English (e.g. 'Haiphong', 'Jebel Ali', 'Busan'), or a 5-character UN/LOCODE (e.g. 'NLRTM')
countryNoOptional 2-letter ISO country code to search in, e.g. 'VN'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful context beyond annotations by stating the return fields, the dataset version, the number of places covered, and that it can both find and verify codes.

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?

The description is front-loaded with a clear 'Use when' clause and then explains the lookup and return details. It is somewhat dense and repeats the UN/LOCODE concept, but every part remains relevant to selecting and interpreting the tool.

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 read-only lookup tool with no output schema, the description provides enough context to call it correctly: input can be a place name or code, output fields are listed, and the dataset scope is stated. It could be more complete about no-match behavior or pagination/limit handling, but the essentials are covered.

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 coverage is 75%, and the schema already documents query as a name or 5-character UN/LOCODE, the type enum, country, and limit. The description reinforces the 5-character code format and gives Busan = KRPUS as an example, but does not add much semantics beyond the schema and does not explain the limit or type parameters further.

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 and resource: finding the 5-character UN/LOCODE of a seaport, airport, or inland container depot. It distinguishes the tool from generic lookups and from sibling code tools by naming UN/LOCODE, port/location codes, and trade-document use cases like bookings and bills of lading.

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?

It gives clear when-to-use guidance: when a user needs a UN/LOCODE for a booking, bill of lading, or invoice, or wants to check a code they were given. It does not explicitly name exclusions or alternative sibling tools, so it misses the top score.

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.

Resources