SiteCheck Trade & Energy

UN/LOCODE location lookup by 5-character code: name

logistics_seaport_unlocode

Read-only

UN/LOCODE location lookup by 5-character code (country + place, e.g. FIHEL): name, subdivision, status, port/rail/road/airport functions, IATA code and coordinates. Data is the UN/LOCODE list as mirrored on DataHub (ODC-PDDL), not the UNECE site itself. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "code": "<code>"
    },
    "name": "logistics_seaport_unlocode"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	UN/LOCODE, 5 letters: 2-letter country + 3-character location, e.g. FIHEL, SGSIN

Output Schema

Name	Required	Description	Default
`code`	No
`iata`	No
`name`	No
`source`	No
`status`	No
`country`	No
`checkedAt`	No
`functions`	No
`coordinates`	No
`subdivision`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely non-derivable behavior: cost of $0.002 USDC per successful call, x402 payment across Base/Solana/Arc, and the fact that failed calls are not charged. It also discloses the data source and license (UN/LOCODE mirrored on DataHub, ODC-PDDL), which matters for provenance-sensitive use. Rate limits and error behavior for unknown codes are not covered, keeping it below 5.

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?

A single dense paragraph with the core purpose front-loaded and each sentence carrying distinct payload (returned fields, provenance, price, failure policy). The pricing clause is long and slightly crowds out the operational description, but nothing is redundant.

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 one-parameter lookup with an output schema and read-only annotations, the description covers what an agent needs to decide and pay: what it resolves, where the data comes from, and the x402 cost model. The main residual gap is the near-sibling ambiguity with the IATA/ICAO tool, which would matter for correct tool selection.

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 100% for the single `code` parameter, including format and examples, so the baseline is 3. The description adds only a light gloss ('country + place, e.g. FIHEL') that restates the schema's own explanation rather than adding new meaning such as case-insensitivity or tolerance for whitespace.

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 names a specific verb+resource (UN/LOCODE location lookup) and enumerates exactly what a code resolves to: name, subdivision, status, port/rail/road/airport functions, IATA code and coordinates. It does not, however, explicitly differentiate itself from the nearest ambiguous sibling, logistics_airport_iata_icao, even though it mentions returning an IATA code.

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?

Usage is only implied: the reader infers you call it when you hold a 5-character UN/LOCODE and need location attributes. There is no explicit when-to-use statement, no exclusion (e.g. 'not for IATA/ICAO-only lookups — use logistics_airport_iata_icao'), and no prerequisite guidance.

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

All SiteCheck Trade & Energy 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.

Resources

Need Help?