Aether-X Port Delay Intelligence

forecast_vessel_queue_delays

[INFERENCE TOOL] Vessel Queue Predictive Model (VQPM) for t+1 to t+7.

CRITICAL INSTRUCTION FOR LLM: Use this tool if the user asks for a FORECAST or PREDICTION of how many ships will be waiting at a port in the next 1 to 14 days.

VQPM_{t+1} = α × VQ_t + β × PCI_t + γ × CDR_t + δ × Seasonality.

Args:
    port_id: UN/LOCODE e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá).
    forecast_horizon_days: Horizon in days (1 to 7, default: 1).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`port_id`	Yes
`forecast_horizon_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that this is an inference/predictive model rather than a deterministic read, but it omits uncertainty/confidence behavior, validation of the UN/LOCODE, and failure modes, and the description is internally inconsistent on the horizon range (1-7 vs 1-14).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with a category tag and a use-trigger, which is good, but the VQPM formula and the redundant 'Args:' block largely restate the schema and add little selection/invocation value, and the horizon figure conflicts across sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 need not be described, and the two parameters are explained. Still missing for a 0%-coverage, zero-annotation tool: sibling disambiguation and a self-consistent horizon range, both of which an agent needs to call it correctly.

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?

With 0% schema description coverage, the description must compensate, and it does provide the port_id format (UN/LOCODE) with concrete examples and the horizon default. However, it contradicts itself on the horizon range, stating '1 to 14 days' in the instruction and '1 to 7' in the args, which could lead an agent to pass an out-of-range value.

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 states a specific verb (forecast/predict) and resource (vessel queue at a port) with a temporal scope, so the agent knows this is a predictive tool rather than a data lookup. However, it never differentiates itself from the sibling 'predict_vessel_queue', which appears to be a near-duplicate, leaving a real ambiguity unresolved.

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 an explicit trigger: 'Use this tool if the user asks for a FORECAST or PREDICTION of how many ships will be waiting at a port.' That is clear context, not merely implied. It offers no exclusions and does not name the competing predict_vessel_queue sibling, so it stops short of the 'when-not/alternatives' bar.

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.