Skip to main content
Glama

OFAC sanctions screening: crypto wallet or name

compliance_sanctions
Read-only

OFAC sanctions (AML/KYC) screening of a crypto wallet or a person, company, vessel or aircraft name against a dated snapshot of the U.S. Treasury SDN and non-SDN Consolidated lists. Address mode: exact match on OFAC-listed digital currency addresses (BTC, ETH/EVM, USDT, TRX, XMR, LTC, more). Name mode: fuzzy match on names and strong aliases ignoring case, accents, punctuation and word order, scored 0-100. Returns match flag, OFAC uid, type, programs, country, list date. Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": "compliance_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPerson, company, vessel or aircraft name, 2 to 120 characters, in Latin script; case, accents, punctuation and word order are ignored. Mutually exclusive with address.
addressNoCrypto wallet address (20 to 120 characters) checked for an exact match against OFAC-listed digital currency addresses; EVM 0x, bech32 and CashAddr addresses match case-insensitively (bitcoincash: prefix optional). Mutually exclusive with name.
thresholdNoMinimum name match score from 70 to 100 (default 85); the score mainly reflects how closely every query word matches a word of the listed name. Name mode only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description goes beyond them by disclosing the dated snapshot nature of the data, fuzzy-matching semantics, and the exact pricing model ($0.01 per successful call via x402 v2, no charge on failure or no-match). That pricing and billing caveat is exactly the kind of context annotations cannot carry, though the return shape is only briefly enumerated.

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-loads purpose and data source, then modes, then return fields, then price - a logical order with no filler. It is dense, packing chain lists and pricing detail into long sentences, but every clause carries information an agent could act on.

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

Completeness4/5

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

With no output schema, the description compensates by listing returned fields (match flag, OFAC uid, type, programs, country, list date). Combined with full schema coverage and read-only annotations, an agent has enough to call it correctly; only detail on result paging or empty-result shape is absent.

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% and the schema already documents mutual exclusivity, character ranges, case/accent handling and the 70-100 threshold default. The description restates the address/name mode split and adds which chains are covered (BTC, ETH/EVM, USDT, TRX, XMR, LTC), but the incremental meaning over the schema is modest, so baseline-plus is appropriate.

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 (OFAC sanctions/AML screening) and precise resources (crypto wallet address or person/company/vessel/aircraft name) against a named data source (U.S. Treasury SDN and non-SDN Consolidated lists). The two operating modes are spelled out, so an agent can tell this apart from sibling tools like wallet_balances or chain_sign_inspect without opening the schema.

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?

Clearly delineates address mode (exact match on OFAC-listed digital currency addresses) versus name mode (fuzzy match, scored 0-100), which is the key routing decision for this tool. It does not name alternative tools or explicitly state exclusions, so it stops short of full alternative-routing guidance.

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