Skip to main content
Glama

Aether-X Port Delay Intelligence

by io.github.belegante-byte
OverviewDiscussionsAdmin

get_shipment_reconstruction

Recover a shipment reconstruction with its full evidence chain (ledger-persisted).

Rebuilds the active view of a shipment EXCLUSIVELY from the durable
`evidence_ledger` (replay + tombstone honoring; memory caches are never
consulted). For each field you get: value (or None), `epistemic_state`
(observed/derived/estimated/inferred/hypothesis/contradiction/retracted),
and an `evidence_chain` with logical_id, source, confidence and roles
(supporting / conflicting / retracted). Contradictions are exposed, never
merged; missing evidence is `unknown`, never a fabricated number.

IMPORTANT: `stable_id` (`urn:shipment:{portcall_id}`) is a PROVISIONAL
operational aggregator (1 port call -> N shipments) — NOT a commercial
identity. `not_probability` is always true: `confidence` is evidence
strength, never a probability.

Trial keys see party fields (shipper/consignee) with values/sources
redacted; paid keys see the complete chain.

Args:
    stable_id: e.g. "urn:shipment:shp_urn:portcall:BRSSZ:unknown".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stable_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: replay + tombstone honoring, memory caches never consulted, contradiction-exposing semantics, no fabricated numbers, and trial-vs-paid key redaction of party fields. This is exactly the behavioral context an agent needs before calling.

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 the core action and constraints, then detail. The prose is dense but each paragraph adds operative information; the trailing 'Args:' line lightly restates the single parameter but is acceptable. Not bloated, though slightly longer than strictly necessary to reach the same clarity.

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?

With an output schema present, the description need not re-explain return shape, and it still covers the epistemic state vocabulary, evidence chain structure, contradiction handling, and access-tier differences. Nothing material is missing for correct invocation.

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 coverage is 0% and the single parameter is undocumented in the schema, but the description compensates with the urn format example and an explicit warning that stable_id is a provisional operational aggregator (1 port call -> N shipments), not a commercial identity. It stops short of stating how to obtain a valid stable_id.

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?

Names a precise verb and resource ('Recover a shipment reconstruction with its full evidence chain') and scopes it as ledger-persisted. It is clearly distinct from the list-oriented sibling list_active_reconstructions and from the risk/evaluation siblings. An agent knows exactly what this returns without opening the schema.

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 implied (recover/rebuild a single shipment's active view from the ledger) but the description never states when to prefer this over list_active_reconstructions or any other sibling, nor any preconditions beyond the key-tier note. Adequate but no explicit when/when-not routing.

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