Skip to main content
Glama

Check a name against OFAC, EU, UN and UK sanctions lists

sanctions
Read-only

Screen one person, company, vessel or aircraft name against the OFAC SDN and Consolidated lists, the EU consolidated list, the UN Security Council list and the UK Sanctions List (official files, refreshed daily). Fuzzy matching with aliases, transliteration and an optional country and date of birth to sharpen the score. Returns each possible match with its list, entry ID, score, programmes and official link. A screening aid, not a legal determination. Price: $0.01 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); 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": {
      "name": "<name>"
    },
    "name": "sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dobNoDate of birth for a person: YYYY-MM-DD, YYYY-MM or YYYY (optional)
nameYesName to screen (person, company, vessel or aircraft), up to 200 characters
typeNoperson or entity (optional, sharpens the score)
listsNoComma-separated lists, default all: ofac-sdn, ofac-consolidated, eu-sanctions-map, un-consolidated, uk-sanctions
countryNoCountry or nationality, ISO code or name (optional, raises or lowers the score)
thresholdNoMatch threshold 50-100, default 85 (lower finds more and more false alarms)

Output Schema

NameRequiredDescriptionDefault
hitNo
queryNo
sourceNo
matchesNo
bestScoreNo
checkedAtNo
disclaimerNo
listsCheckedNo
listsVersionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses data provenance and freshness ('official files, refreshed daily'), matching behavior (fuzzy, aliases, transliteration), the shape of the response, and the cost model including that failed calls are not charged. The legal caveat and payment mechanism are exactly the kind of operational context annotations cannot convey.

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?

Purpose and list coverage are front-loaded, then matching behavior, then return content, then caveat and price. Each sentence carries distinct information an agent needs (freshness, fuzzy behavior, cost) and nothing is repeated from the schema.

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 paid, open-world screening tool with an output schema already covering return values, the description supplies everything else that matters: which lists, how matching works, cost and payment, failure billing, and a legal disclaimer. Nothing an agent needs to invoke it responsibly is missing.

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?

Schema description coverage is 100%, so every parameter is already documented, including the threshold range and list identifiers. The description only echoes that country and date of birth sharpen the score, adding no syntax or interaction detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb ('Screen') and resource ('one person, company, vessel or aircraft name') and enumerates exactly which lists are consulted (OFAC SDN/Consolidated, EU consolidated, UN SC, UK Sanctions List). The scope is unambiguous and no sibling in the catalog overlaps with sanctions screening.

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 establishes the context of use (name screening) and sets a boundary with 'A screening aid, not a legal determination', plus hints that optional country/dob sharpen results. It does not name an alternative tool or state explicit when-not-to-use conditions, so it falls short of a 5.

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