Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Estimate vessel ETA

maritime-intelligence_vessel-eta-estimate

Estimate ETA from the latest caller-supplied AIS point to a destination using geodesic distance and SOG or assumed speed. Price $0.04 USDC. POST /api/v1/maritime-intelligence/vessel-eta-estimate. 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_vessel-eta-estimate"
  }
}

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
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the operationally critical traits: price ($0.04 USDC), the payment gate (unpaid calls return 402 and do not run), and the computation basis (geodesic distance, SOG else assumed speed). It stops short of describing the response payload or behavior when no AIS point is supplied, so it is not fully transparent.

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?

Three tight sentences, front-loaded with purpose and method, then price, endpoint, and payment behavior. No filler and nothing redundant.

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 tool with 20 optional parameters, deep nested objects, no output schema, and no annotations, the description is too thin. It does not say what is returned (ETA, distance, effective speed), which parameter subset actually drives the estimate, or whether the many unrelated arrays (cargo, demurrage, sanctions) are ignored, leaving an agent unable to construct a correct call confidently.

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 gives meaning to only a handful — the AIS points, destination coordinates, and assumed speed — while vessels, waypoints, portSamples, cargoEvents, demurrageCases, fetchOfac, the csv/json/text/file passthrough fields, and the gap/deviation thresholds are never explained.

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?

States a specific verb+resource ('Estimate ETA' for a vessel) and the method used: geodesic distance from the latest caller-supplied AIS point, using SOG or an assumed speed. It does not explicitly name a sibling it differs from (e.g. route-deviation-detect or voyage-risk-report), but the purpose is unambiguous.

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 only implied: 'caller-supplied AIS point' hints that the caller must provide data rather than have the service fetch it. There is no explicit when-to-use/when-not guidance versus alternatives such as route-deviation-detect, and no stated prerequisite such as needing an SOG or assumedSpeedKn fallback.

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