Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Reconcile cargo shipment events

maritime-intelligence_cargo-shipment-event-reconcile

Reconcile document-side and ops-side caller-supplied cargo shipment events by shipment/BL, event type, time, location, and quantity. Price $0.04 USDC. POST /api/v1/maritime-intelligence/cargo-shipment-event-reconcile. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "maritime-intelligence_cargo-shipment-event-reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
vesselsNo
aisPointsNo
fetchOfacNo
waypointsNo
cargoEventsNo
portSamplesNo
assumedSpeedKnNo
demurrageCasesNo
destinationLatNo
destinationLonNo
ownershipRecordsNo
sanctionsEntriesNo
gapThresholdHoursNo
deviationThresholdKmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.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 full burden, and it does disclose the pricing ($0.04 USDC), the payment gating (unpaid calls return 402 and do not run), and the HTTP route - genuinely useful operational context an agent cannot get elsewhere. It does not disclose what reconciliation produces, whether mismatched or unmatched events are reported or dropped, or any tolerance used when comparing times and quantities. That leaves significant behavioral gaps for a compute-heavy tool with no annotations.

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?

Four short sentences, zero filler, with the core purpose front-loaded before pricing and endpoint details. The price and 402 note are terse and useful rather than padding. It loses a point only because the endpoint URL restates the tool name without adding decision value.

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

Completeness2/5

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

For a 20-parameter tool with no annotations, no output schema, and nested object inputs, the description is too thin: an agent cannot tell which inputs actually drive the reconciliation, whether the many optional collections are ignored, or what the response contains. The billing and 402 details are good but do not substitute for input requirements or output expectations.

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

Parameters2/5

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

Schema description coverage is 0% across 20 parameters, so the description must compensate and largely does not. It explains the matching fields (shipment/BL, event type, time, location, quantity), which map to cargoEvents item properties, but says nothing about the other 19 top-level parameters - csv/text/json/file/files envelope fields, vessels, aisPoints, waypoints, portSamples, demurrageCases, ownershipRecords, sanctionsEntries, thresholds, asOf, fetchOfac - or which are required versus ignored by this tool.

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?

Names a specific verb ("Reconcile") plus the resource ("cargo shipment events") and states the matching keys: shipment/BL, event type, time, location, quantity, and the two sides being compared (document vs ops). That is enough for an agent to distinguish it from siblings like demurrage-cost-calculate or vessel-eta-estimate, which do different jobs. It stops short of a 5 because it never explicitly says what to use instead when events are already reconciled or when the data lives in a sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no prerequisites are stated (e.g., that cargo events must be supplied by the caller in the request body). "Caller-supplied" hints at the input source, implying usage, but an agent gets no routing rule or precondition beyond that. Compared to the calibration example of a settings-update tool that also scored 2, this is equivalent: implied but unstated usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources