Aether-X Port Delay Intelligence

evaluate_charter_risk

[DECISION TOOL] Evaluate charter risk and demurrage financial exposure under explicit assumptions.

Returns a DecisionResult (decision-result.v1) with:
- exposure.value: estimated exposure in USD
- exposure.basis: calculation rationale
- assumptions: all stated premises (demurrage rate, laytime)
- physical_basis: list of verified physical observations supporting the estimate
- uncertainties: explicit list of what is NOT known (charter party, actual laytime, cargo quantity)

Args:
    port_id: UN/LOCODE e.g. "BRPNG" (Paranaguá).
    commodity: Commodity type e.g. "SOJA", "MILHO", "CONTEINERES".
    demurrage_rate_usd_day: Demurrage rate in USD/day (default: 32000).
    expected_laytime_days: Agreed laytime in days (default: 2.0).

Input Schema

TableJSON Schema

Name	Required	Default
`port_id`	Yes
`commodity`	No	SOJA
`expected_laytime_days`	No
`demurrage_rate_usd_day`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden, and it handles this well: it specifies the DecisionResult output, details that assumptions and uncertainties are explicit, and mentions verified physical observations as the basis. It stops short of declaring side effects or read-only behavior, but for an evaluation tool this is less critical.

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

Conciseness5/5

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

The description is front-loaded with a one-line purpose, then uses a compact bulleted list for output fields and an Args block for parameters. Every section contributes information; there is no filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter decision tool with no annotations, the description covers all inputs, defaults, output fields, calculation rationale, and explicit uncertainties. The output schema exists, but the description's output breakdown is still useful; there are no major gaps an agent would face before calling it.

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 schema only provides titles and defaults, so the description is the sole source of parameter meaning. It gives the UN/LOCODE format plus a concrete example for port_id, commodity examples, and units for demurrage and laytime, which is exactly what an agent needs.

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 opening line names a specific action and resource: it evaluates charter risk and demurrage financial exposure, and the [DECISION TOOL] tag signals its role. The resource is specific enough to distinguish it from siblings like evaluate_routing_alternatives or get_port_risk, even though no sibling is named.

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 description never states when to choose this tool over sibling tools such as get_port_risk or evaluate_routing_alternatives, nor does it give exclusion criteria. The purpose statement implies its use for charter/demurrage decisions, but the guidance 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.