Skip to main content
Glama

Antigravity x402 & MCP Gateway

screen_ofac_sanctions

[0.006000 USDC via x402] Screens any individual, company, vessel, or Base/Ethereum/Bitcoin/Solana/Tron cryptocurrency wallet address against the live US Treasury OFAC Specially Designated Nationals (SDN) list in under 15 ms.

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": {
      "query": "<query>"
    },
    "name": "screen_ofac_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPerson, company, organization, vessel name, or cryptocurrency wallet address to screen against OFAC SDN.
min_scoreNoFuzzy token-coverage match threshold between 0.50 and 1.00 (default 0.75).
wallet_addressNoOptional explicit EVM (0x...) or Solana/Bitcoin address for exact OFAC Digital Currency Address matching.
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.006000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the paid model (0.006000 USDC via x402) and claimed latency (<15 ms) against a live list, but says nothing about whether this is a read-only lookup, what a hit versus a miss returns, whether match scores are included, or how the payment handshake behaves — all left to the schema.

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?

A single tight sentence with no filler; the subject scope is front-loaded and the latency claim closes it cleanly. Leading with the price string is unconventional but is genuinely decision-relevant for an agent, so it earns its place.

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

Completeness3/5

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

There is no output schema, so the description should at minimum characterize the response (match/no-match verdict, score field, list metadata). It omits that entirely, and with zero annotations it also omits any safety or mutation profile. What is present is accurate but stops short of what an agent needs to interpret results.

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 all four parameters (query, min_score, wallet_address, x402_payment_signature) are already documented in structured form. The description adds no syntax, format, or tuning guidance beyond echoing the entity types; baseline 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 ('Screens'), a specific resource ('live US Treasury OFAC Specially Designated Nationals (SDN) list'), and the scope of accepted subjects (individuals, companies, vessels, six named wallet chains). This is distinguishable at a glance from siblings such as check_cisa_kev_exploits or verify_gleif_lei_entity 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 Guidelines3/5

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

The description implies usage through the list of screenable entity types, but never says when to prefer this over alternatives (e.g., LEI/GLEIF verification or CISA KEV lookups) or when screening is unnecessary. No exclusion cases or prerequisites are stated, leaving the agent to infer the trigger condition.

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.