SiteCheck Trade & Energy

Searches the US OFAC Specially Designated Nationals list

logistics_sanctioned_vessel_check

Read-only

Searches the US OFAC Specially Designated Nationals (SDN) list for vessels by name or IMO number and returns matching vessel entries (sanctions programs, flag, vessel type, owner, gross tonnage, call sign, IMO, aliases), via the US Consolidated Screening List. Only the OFAC SDN list; not the UN, EU or UK lists, and an empty result is not a clearance. Related tools on this server, for a different need: logistics_imo_vessel_dossier when you need ship particulars by IMO number: name, type, flag, MMSI; logistics_vessel_tracker when you need live AIS position, speed, heading and voyage status for one. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "logistics_sanctioned_vessel_check"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Vessel name (3+ characters) or IMO number (7 digits)
`limit`	No	1 to 20, default 10

Output Schema

Name	Required	Description	Default
`count`	No
`query`	No
`source`	No
`matches`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the returned fields, the specific sanctions list covered, the meaning of empty results, and the pricing model including that failed calls are not charged. This adds meaningful operational context for a high-stakes screening tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then adds scope exclusions, output fields, sibling-tool routing, and pricing without obvious filler. Although dense, every sentence carries information relevant to correct selection or invocation.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a sanctions-screening tool with an output schema and read-only annotations, the description covers the key gaps: list scope, empty-result caveat, returned data, alternative tools, and call pricing. An agent has enough context to decide when to use it and what the result does and does not mean.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% parameter description coverage, including the 3+ character vessel name or 7-digit IMO number and the limit range/default. The description restates the name-or-IMO lookup mode but adds little beyond the schema for the two parameters, so it meets the baseline rather than substantially improving parameter understanding.

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 states a precise verb, resource, and scope: it searches the OFAC SDN list for vessels by name or IMO number. It also clearly distinguishes this tool from related vessel lookup and tracking tools, so an agent can identify its purpose without checking sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly limits the tool to the OFAC SDN list, excludes the UN, EU, and UK lists, and warns that an empty result is not a clearance. It also names alternative tools with the exact conditions under which they should be used instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Trade & Energy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?