Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Check vessel sanctions signals

maritime-intelligence_vessel-sanctions-signal-check

Screen caller-supplied vessel/owner/operator names and IMOs against caller sanctions entries or optional key-free OFAC SDN names. Not a legal determination. Price $0.05 USDC. POST /api/v1/maritime-intelligence/vessel-sanctions-signal-check. 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-sanctions-signal-check"
  }
}

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 delivers real operational context: $0.05 USDC pricing, unpaid calls returning HTTP 402 without executing, the POST endpoint, and a legal disclaimer. What it omits is matching behavior (exact vs fuzzy name matching, how IMO vs name collisions are handled) and the response shape, so it falls short of 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?

The purpose is front-loaded in the first sentence and each following sentence adds a distinct fact (legal caveat, price, endpoint, payment failure mode). It is terse and telegraphic rather than padded, though the staccato fragments read more like a spec sheet than prose.

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

Completeness3/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 annotations and no output schema, the description covers the commercial and payment essentials well. It leaves significant gaps: which of the many entity/event arrays actually influence screening, whether fetchOfac requires network/key handling, and what the response contains.

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, many of them nested arrays (aisPoints, cargoEvents, portSamples, demurrageCases, ownershipRecords, waypoints). The description only touches vessels names/owners/operators/IMOs, sanctionsEntries and fetchOfac, leaving the bulk of params — including csv/json/text/file input channels and asOf — unexplained anywhere.

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 scope: 'Screen caller-supplied vessel/owner/operator names and IMOs against caller sanctions entries or optional key-free OFAC SDN names.' That tells an agent exactly what the tool does and what entities and reference data it operates on. It does not explicitly distinguish itself from the nearest-sounding sibling (voyage-risk-report), so it stops short of a 5.

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?

It gives context that sanctions entries can be caller-supplied or fetched via an optional key-free OFAC source, and warns this is 'not a legal determination', which hints at the boundary of the tool's role. However, it never states when to prefer this over the sibling risk/normalize tools or what input shape is expected, so usage is implied rather than guided.

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