Skip to main content
Glama

Aether-X Port Delay Intelligence

by io.github.belegante-byte
OverviewDiscussionsAdmin

evaluate_corridor_risk

[DECISION TOOL] Evaluate full global trade corridor risk (e.g. Chicago/Brazil -> China/Europe).

Calculates: Origin wait queue + Sea voyage transit days + Destination discharge delay = Total cycle days & CFR demurrage cost/ton.

Args:
    origin_port: Export port UN/LOCODE e.g. "BRPNG" (Paranaguá), "BRSSZ" (Santos).
    destination_port: Import port UN/LOCODE e.g. "CNTAO" (Qingdao), "CNNGB" (Ningbo), "NLRTM" (Rotterdam).
    commodity: Commodity type e.g. "SOJA", "MILHO".
    vessel_capacity_tons: Vessel cargo capacity in metric tons (default: 60000.0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commodityNoSOJA
origin_portYes
destination_portYes
vessel_capacity_tonsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does state the calculation model clearly, which signals a read-only evaluation, but it does not mention limitations, data freshness, or what happens for unsupported ports or commodities.

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 well-structured and front-loaded: purpose first, then the formula, then a compact parameter list. Every sentence earns its place, though the arg list could have been slightly tighter.

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?

The output schema covers return values, so the description does not need to explain them. All four parameters are documented with useful examples. The main missing context is explicit guidance on when to choose this tool over the closely related sibling tools.

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

Parameters4/5

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

Schema description coverage is 0%, so the parameter explanations are essential. The description adds real meaning: UN/LOCODE format, concrete port examples, commodity examples, and the default vessel capacity. It stops short of documenting valid commodity enums or validation constraints.

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 opens with a specific verb and resource: 'Evaluate full global trade corridor risk', and then states exactly what is calculated (Origin wait queue + Sea voyage transit days + Destination discharge delay = Total cycle days & CFR demurrage cost/ton). This clearly distinguishes it from the sibling port-level and charter-risk tools.

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 '[DECISION TOOL]' label and the 'full global trade corridor' scope imply when the tool is appropriate, but the description never explicitly says when to use this over evaluate_charter_risk or get_port_risk. There are no alternatives named and no exclusion conditions.

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 toolsInspect
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