Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Normalize vessel ownership history

maritime-intelligence_vessel-ownership-history-normalize

Normalize caller-supplied vessel ownership timeline rows and flag overlapping intervals. Registry filings are not invented. Price $0.03 USDC. POST /api/v1/maritime-intelligence/vessel-ownership-history-normalize. 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-ownership-history-normalize"
  }
}

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.1/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; it does disclose the $0.03 USDC cost and that unpaid calls return 402 without running, which is genuinely useful. It also discloses one output behavior (overlap flagging) and a non-fabrication constraint, but says nothing about determinism, how intervals are ordered/adjusted, or error handling beyond the payment failure.

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?

The core capability is stated first, followed by scope, price, endpoint, and failure mode in compact sentences with no filler. The payment and routing details consume roughly half the text but are arguably necessary for invocation.

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, deeply nested tool with no annotations and no output schema, the description leaves far too much open: it never explains what normalized output rows look like (beyond overlap flags) or which of the many array inputs are honored. Only routing, pricing, and one behavioral rule are covered.

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, and the description only points at one of them ('ownership timeline rows'). The remaining input surface — vessels, aisPoints, waypoints, cargoEvents, portSamples, demurrageCases, sanctionsEntries, asOf, file/files, gapThresholdHours, deviationThresholdKm, assumedSpeedKn — is undocumented in both the schema and the description, so an agent cannot tell which inputs actually matter for this operation.

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?

The description gives a specific verb and object ('Normalize caller-supplied vessel ownership timeline rows') plus a concrete secondary behavior ('flag overlapping intervals'), which lets an agent separate it from identity, sanctions, or ETA siblings. It stops short of explicitly naming a sibling, so it is clear but not fully differentiated.

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 ... rows' and 'Registry filings are not invented' signal that this tidies input you already hold rather than enriching or fetching registry data. There is no explicit when-to-use versus alternatives such as vessel-identity-normalize or sanctions-signal-check, and no stated preconditions.

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