Skip to main content
Glama

sanctions-screening-mcp-server

sanctions-screening-mcp-server: screen identifier

sanctions_screen_identifier
Read-onlyIdempotent

Look up an identifier — a vessel or company IMO number, a SWIFT/BIC code, a digital-currency wallet address, a passport or national ID number, or any other identifier a list publishes — against loaded sanctions and export-control watchlists — OFAC SDN + Consolidated, EU, UK, UN, and the six BIS/State CSL lists. Check sanctions_list_sources for coverage. Exact match after normalization, with no fuzzy or partial matching and no score: spacing, letter case, and the separators - . / are ignored, an IMO number matches with or without its IMO prefix, a SWIFT/BIC code compares on its first eight characters so a branch code matches its institution, and a wallet address folds case only where its encoding is case-insensitive (hex, bech32, cashaddr — never base58). Returns every designation that publishes a matching identifier, one per designation — an OFAC party both OFAC lists publish under one entry ID is one hit, its sources naming both lists — with the identifiers that matched as published; sanctions_get_designation pulls the full record. This is a screening AID for a human/compliance review, NOT a compliance determination: a hit means "review this candidate against the official source," and an empty result never means "cleared" — an identifier a list prints only in free-text remarks, or bundled with other numbers in one field, does not match.

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": {
      "value": "<value>"
    },
    "name": "sanctions_screen_identifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRestrict to one identifier category, or "any" (default) to search all published identifiers, including MMSI, call signs, tax and registration numbers. Published label categories take precedence. An otherwise unclassified label with an IMO prefix and exactly seven digits is indexed as imo, including company numbers.any
valueYesThe identifier to look up, as you hold it (e.g. "IMO 7406784", "DCBKKPPY", a wallet address, a passport number). Must contain at least one character other than whitespace and - . /
sourcesNoRestrict to specific source lists. Omit to search all loaded lists.

Output Schema

NameRequiredDescriptionDefault
hitsNoDesignations that publish a matching identifier, one per designation (an OFAC party on both OFAC lists once), ordered by source list then entry ID. Not paged — the most widely shared published identifiers map to about a dozen designations.
errorNoPresent when the call failed. Absent on success.
caveatNoDecision-support caveat — this is a screening aid, not a compliance determination.
noticeNoGuidance when no designation matched — what to try next, and what an empty result does NOT mean.
totalCountNoNumber of designations returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Restrict to one identifier category, matched on the label each list publishes, or \"any\" (default) to search every published identifier, including categories with no name here (MMSI, call signs, tail numbers, tax and registration numbers, email, websites)."New value: +"Restrict to one identifier category, or \"any\" (default) to search all published identifiers, including MMSI, call signs, tax and registration numbers. Published label categories take precedence. An otherwise unclassified label with an IMO prefix and exactly seven digits is indexed as imo, including company numbers."
  2. Changed3 schema fields changed
    • changedInput schema / properties / sources / items / enum
      Previous value: -[
      -  "ofac_sdn",
      -  "ofac_consolidated",
      -  "eu",
      -  "uk",
      -  "un"
      -]New value: +[
      +  "ofac_sdn",
      +  "ofac_consolidated",
      +  "eu",
      +  "uk",
      +  "un",
      +  "bis_el",
      +  "bis_dpl",
      +  "bis_uvl",
      +  "bis_meu",
      +  "state_dtc",
      +  "state_acn"
      +]
    • changedOutput schema / properties / hits / items / properties / source / enum
      Previous value: -[
      -  "ofac_sdn",
      -  "ofac_consolidated",
      -  "eu",
      -  "uk",
      -  "un"
      -]New value: +[
      +  "ofac_sdn",
      +  "ofac_consolidated",
      +  "eu",
      +  "uk",
      +  "un",
      +  "bis_el",
      +  "bis_dpl",
      +  "bis_uvl",
      +  "bis_meu",
      +  "state_dtc",
      +  "state_acn"
      +]
    • changedOutput schema / properties / hits / items / properties / sources / items / enum
      Previous value: -[
      -  "ofac_sdn",
      -  "ofac_consolidated",
      -  "eu",
      -  "uk",
      -  "un"
      -]New value: +[
      +  "ofac_sdn",
      +  "ofac_consolidated",
      +  "eu",
      +  "uk",
      +  "un",
      +  "bis_el",
      +  "bis_dpl",
      +  "bis_uvl",
      +  "bis_meu",
      +  "state_dtc",
      +  "state_acn"
      +]
  3. Changed4 schema fields changed
    • changedOutput schema / properties / hits / description
      Previous value: -"Designations that publish a matching identifier, one per designation, ordered by source list then entry ID. Not paged — the most widely shared published identifiers map to about a dozen designations."New value: +"Designations that publish a matching identifier, one per designation (an OFAC party on both OFAC lists once), ordered by source list then entry ID. Not paged — the most widely shared published identifiers map to about a dozen designations."
    • changedOutput schema / properties / hits / items / properties / source / description
      Previous value: -"Which watchlist this candidate is on — its provenance."New value: +"The watchlist whose record this hit's fields come from — its provenance. For an OFAC party both OFAC lists publish, ofac_sdn unless the Consolidated record matched alone; sources names every list."
    • addedOutput schema / properties / hits / items / properties / sources
      Added value: +{
      +  "description": "Every screened list this candidate is on, in list order: one list, or ofac_sdn and ofac_consolidated together for an OFAC party both OFAC lists publish under one entry ID — one hit, not two. Read this, not source, for every list; the entry ID resolves in sanctions_get_designation under each.",
      +  "items": {
      +    "enum": [
      +      "ofac_sdn",
      +      "ofac_consolidated",
      +      "eu",
      +      "uk",
      +      "un"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / hits / items / required
      Previous value: -[
      -  "source",
      -  "sourceLabel",
      -  "sourceEntryId",
      -  "primaryName",
      -  "entityType",
      -  "matchedIdentifiers"
      -]New value: +[
      +  "source",
      +  "sourceLabel",
      +  "sourceEntryId",
      +  "sources",
      +  "primaryName",
      +  "entityType",
      +  "matchedIdentifiers"
      +]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnly/idempotent/closed-world, and the description adds substantial behavior beyond them: exact match only, no fuzzy or scoring, the specific normalization rules (spacing, case, -, ., / separators, IMO prefix optional, SWIFT first-eight comparison, case folding only for hex/bech32/cashaddr), one hit per designation with source attribution, and the explicit false-negative caveat for free-text or bundled identifiers. That is far more than the annotations supply.

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?

Front-loaded with purpose and identifier scope, followed by matching semantics and then the interpretation caveat; every clause carries information. The single dense paragraph is long and the normalization rules are packed tightly, which slightly taxes readability, but nothing is redundant.

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 read-only screening tool with full schema coverage and an output schema, this is complete: coverage of sources, matching semantics, result cardinality, and the critical limitations of the result are all stated. An agent could call it and correctly interpret a hit or miss without consulting anything else.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about how the 'value' parameter is interpreted — normalization, prefix tolerance, truncation for BIC, and case folding rules that determine whether a submitted string can match. It does not further elaborate the 'sources' or 'type' parameters beyond what the schema already documents.

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 opens with a specific verb and resource ('Look up an identifier') and immediately enumerates the identifier families covered (IMO, SWIFT/BIC, wallet, passport, national ID) plus the exact watchlists searched. It is clearly distinguishable from sanctions_screen_name by scoping itself to published identifiers, and it names sanctions_get_designation and sanctions_list_sources as related tools.

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

Usage Guidelines4/5

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

It gives explicit routing guidance ('Check sanctions_list_sources for coverage', 'sanctions_get_designation pulls the full record') and a strong when-to-trust rule: a hit means review against the official source and an empty result never means cleared. It does not explicitly state the inverse case ('for a person's name, use sanctions_screen_name'), so the alternative-selection guidance is implied rather than fully spelled out.

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.