Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Normalize vessel identity

maritime-intelligence_vessel-identity-normalize

Normalize caller-supplied vessel name, IMO, MMSI, call sign, flag, owner, and operator fields. Validates IMO checksum when an IMO is supplied. Paid AIS coverage is not used. Price $0.03 USDC. POST /api/v1/maritime-intelligence/vessel-identity-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-identity-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.3/5.0
Behavior4/5

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

With no annotations to lean on, the description discloses several important behavioral traits: IMO checksum validation, the absence of paid AIS coverage, a $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. It does not explain output format or what happens when checksum validation fails, but it adds substantial operational context beyond the empty annotation set.

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 description is front-loaded with the core action and scope, then adds validation, data-source, pricing, and endpoint details in a compact sequence. Every sentence carries relevant information for an agent. The only minor inefficiency is that the endpoint and payment behavior are API-level details that could be separated from the functional description.

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?

The tool has a complex input schema with nested objects, 20 optional parameters, no output schema, and no annotations. The description covers the core normalization purpose and some operational behavior, but it does not clarify why the many unrelated arrays (cargoEvents, portSamples, demurrageCases, etc.) exist or whether they are ignored by this tool. For an agent to call this correctly, it needs guidance on which subset of the schema actually matters.

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 carry the burden. It only mentions the vessel identity fields (name, IMO, MMSI, call sign, flag, owner, operator) that map to the nested vessels array. It leaves many parameters unexplained, including csv, json, text, file/files, aisPoints, fetchOfac, waypoints, cargoEvents, portSamples, demurrageCases, ownershipRecords, sanctionsEntries, asOf, destination coordinates, and threshold parameters.

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 opens with a specific verb and resource: 'Normalize caller-supplied vessel name, IMO, MMSI, call sign, flag, owner, and operator fields.' It clearly distinguishes the tool from data-enrichment siblings by stating 'Paid AIS coverage is not used.' It does not explicitly name sibling tools, but the purpose and scope are 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 implied: call it when you have caller-supplied vessel identity fields to normalize. The note that 'Paid AIS coverage is not used' helps set expectations and indirectly separates it from AIS-based siblings. However, there is no explicit when-to-use vs when-not-to-use guidance and no named alternative for related tasks such as ownership-history normalization.

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