Aether-X Port Delay Intelligence

get_port_risk

Assess CURRENT congestion and delay risk at a single seaport.

Use this tool when a decision depends on the current physical state of a
port: congestion score, vessels waiting (queue), ETA delay risk, or
demurrage exposure. Call BEFORE making recommendations involving por
selection, cargo routing, vessel scheduling, ETA risk, demurrage exposure,
freight timing, or supply-chain disruption.

Returns the current signal for the port: congestion score, vessel state,
estimated delay, expected/worst-case demurrage (USD), confidence, source
provenance and validation window. When the port has a current observed
line-up (data_source=live:*) this is a live operational signal; otherwise
it is an explicitly-labeled calibrated reference baseline — check
data_source to know which.

Args:
    port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá), "CNSHA" (Shanghai).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`port_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses the return signal set, and critically explains the data_source=live:* vs. calibrated-reference-baseline distinction so the agent knows how much to trust the output. This is exactly the provenance/auth-adjacent context an agent needs and cannot get from structured fields.

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 purpose, then usage, then return shape, then args — a sensible order with no filler sentences. Slightly verbose in the repeated list of decision contexts, but every block 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?

An output schema exists so return values needn't be restated, yet the description still usefully frames them and adds the trust-level caveat. Combined with full usage and parameter guidance, an agent has everything needed to call and interpret this correctly; minor room remains around failure/coverage cases (e.g., unsupported ports).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter is bare, but the description fully compensates: it names port_id, specifies the UN/LOCODE format, and supplies three concrete examples (BRSSZ, BRPNG, CNSHA). The agent can construct a valid call without guessing.

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?

States a specific verb+resource+scope: 'Assess CURRENT congestion and delay risk at a single seaport.' The 'single seaport' framing distinguishes it from plural siblings like get_ports_risk, and the enumerated signal set (congestion score, queue, ETA delay, demurrage) pins down exactly what it produces.

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?

Explicitly states when to use it ('when a decision depends on the current physical state of a port') and enumerates the downstream decisions that should call it first (port selection, cargo routing, vessel scheduling, ETA risk, demurrage, freight timing). Nothing about invocation context is left to inference.

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

All Aether-X Port Delay Intelligence 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.