Skip to main content
Glama

OFAC sanctions screen (x402)

OFAC sanctions screen in one call against the US Treasury SDN list: by name (also matches aliases) or by crypto address

sanctions_check
Read-onlyIdempotent

OFAC sanctions screen in one call against the US Treasury SDN list: by name (also matches aliases) or by crypto address (SDN-listed digital currency addresses): matches with entity number, type, program, remarks (name=Acme Trading or address=0x...). Screening aid, not a compliance determination. Pay per call $0.002 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
nameNoperson or company name
addressNoor a crypto address, 0x...
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the read-only, open-world, idempotent, and non-destructive annotations, it discloses alias matching, the SDN-listed scope of address screening, returned match fields, and the per-call price, currency, network, and payment protocol. It leaves matching precision, list freshness, and no-match behavior unspecified.

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 description front-loads the operation and source, then covers inputs, outputs, limitations, and cost without filler. Its single long sentence is dense and closely repeats the title, but nearly every clause provides useful information.

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?

For a simple three-parameter paid read, the description and schema together support tool selection and invocation, including the first-call x402 payment flow, while annotations establish the safety profile. Listing match fields partly compensates for the missing output schema, though input-combination and matching semantics remain ambiguous.

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?

Although schema coverage is 100%, the description adds that name searches also match aliases, clarifies that addresses are SDN-listed digital currency addresses, and provides concrete invocation examples. It also explains payment economics, but does not state whether name and address may be supplied together or how conflicts are handled.

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 specifies the screening action, the US Treasury SDN data source, both lookup modes, and the fields returned for matches. It does not explicitly contrast itself with the broader us_treasury sibling, so it is clear but not fully differentiating.

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?

The wording 'by name ... or by crypto address' establishes the supported use cases, while 'Screening aid, not a compliance determination' states an important limitation. It does not identify alternatives or exclusions such as non-OFAC sanctions lists or cases requiring authoritative compliance review.

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