Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Detect vessel route deviations

maritime-intelligence_vessel-route-deviation-detect

Compare caller-supplied AIS points to planned waypoints and flag points beyond a distance threshold. Price $0.04 USDC. POST /api/v1/maritime-intelligence/vessel-route-deviation-detect. 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-route-deviation-detect"
  }
}

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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does add genuinely useful commercial behavior (price $0.04 USDC, POST endpoint, unpaid calls return 402 and do not execute), but it says nothing about what the output contains, how points are matched to waypoints, or what happens with partial data. For a 20-parameter analytics tool with zero annotation coverage, this is a significant gap.

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 short sentences with the functional purpose front-loaded and no filler. The endpoint path is arguably redundant with the tool name, but pricing and the 402 behavior justify their space.

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?

There is no output schema and no annotations, so the description should explain what flagged results look like and how the alternate bulk-input parameters interact with the structured ones. Instead it covers only the happy-path summary, leaving most of a 20-parameter surface unexplained.

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 it does not. It only gestures at three inputs (aisPoints, waypoints, a distance threshold), leaving csv/json/text/file/files, asOf, vessels, cargoEvents, portSamples, assumedSpeedKn, destinationLat/Lon, gapThresholdHours, and the sanctions/ownership arrays entirely undocumented in both places.

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 description gives a specific verb and both operands: it compares caller-supplied AIS points against planned waypoints and flags points beyond a distance threshold. This is a concrete, distinguishable function, clearly separable from a sibling like ais-track-gap-detect, which concerns gaps rather than route geometry.

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: the agent must infer it needs both AIS points and waypoints supplied and a threshold chosen. There is no explicit statement of when to prefer this over track-gap detection or voyage-risk-report, and no prerequisites or data-format guidance beyond payment.

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