Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Detect AIS track gaps

maritime-intelligence_ais-track-gap-detect

Detect time gaps and implied speeds between caller-supplied AIS points. Global real-time AIS coverage is not claimed. Price $0.04 USDC. POST /api/v1/maritime-intelligence/ais-track-gap-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_ais-track-gap-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

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does add real value: price ($0.04 USDC), the POST endpoint, and a clear 402-on-unpaid refusal that means the call does not execute. It omits what the analysis returns and how thresholds affect results, so it is partial rather than complete.

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, front-loaded with the purpose, then scope, then price/route, then payment behavior. No filler, though the endpoint and price occupy space that could have gone to parameter guidance.

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

Completeness1/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 nested objects, no output schema, and zero schema description coverage, the description leaves the agent without any guidance on which of the many input families are required or how gaps/speeds are computed. This is materially insufficient for correct invocation.

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?

20 parameters at 0% schema description coverage, yet the description only gestures at 'AIS points' and 'implied speeds'. It says nothing about the csv/json/text/file input alternatives, gapThresholdHours, assumedSpeedKn, or the many unrelated-looking arrays (cargoEvents, demurrageCases, portSamples) that an agent must decide whether to supply.

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 clear verb and resource: 'Detect time gaps and implied speeds between caller-supplied AIS points.' The 'caller-supplied' qualifier distinguishes it from tools that fetch their own AIS data, though it does not name any sibling it competes with.

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?

No when-to-use or when-not-to-use guidance relative to siblings such as vessel-route-deviation-detect or vessel-eta-estimate. The only scope statement ('Global real-time AIS coverage is not claimed') limits expectations but does not tell the agent when this tool is the right choice.

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