Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Build maritime voyage risk report

maritime-intelligence_voyage-risk-report

Aggregate identity, AIS gaps, route deviation, port congestion, ETA, demurrage, sanctions signals, cargo reconciliation, and ownership history from caller-supplied records only. Price $0.08 USDC. POST /api/v1/maritime-intelligence/voyage-risk-report. 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_voyage-risk-report"
  }
}

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

B3.4/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 payment gate, the endpoint, and the exact failure mode (402, no execution) – useful operational context beyond a bare description. It omits what the report returns and how results are structured, and the 'caller-supplied records only' claim sits uneasily with the fetchOfac parameter, which implies an external OFAC lookup.

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?

Three sentences, front-loaded with what is aggregated, followed by price, endpoint, and failure behavior – a sensible ordering with no filler. The opening enumeration is long but each named signal earns its place by telling the agent which record types to supply.

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?

For a 20-parameter aggregator with no annotations and no output schema, the description covers purpose, data provenance, cost, and failure mode, and the signal list incidentally sketches the report's contents. It leaves the low-coverage parameters and the exact response shape undocumented, which is a real gap for a tool this complex.

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?

Schema description coverage is 0% across 20 parameters, so the description must compensate; the enumerated signal domains do map meaningfully onto the main input families (aisPoints, waypoints, portSamples, demurrageCases, sanctionsEntries, cargoEvents, ownershipRecords, vessels). Thresholds (gapThresholdHours, deviationThresholdKm), assumedSpeedKn, asOf, fetchOfac, and the csv/json/text/file/files blob inputs get no explanation at all.

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 (aggregate) and a concrete output artifact (voyage risk report), then enumerates the nine signal domains it fuses, which distinguishes it from the single-analysis siblings listed. It stops short of explicitly saying 'use this instead of calling the individual analyzer tools,' so differentiation is implied rather than stated.

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?

States two hard constraints an agent must know: all inputs are caller-supplied records, and payment is required ($0.08 USDC, 402 on unpaid calls). However, it never says when to reach for this aggregator versus composing the individual sibling tools, nor what inputs it needs at minimum given all 20 parameters are optional.

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