Skip to main content
Glama
Sign In

Public Domain Check

by io.github.chomkaevan
OverviewDiscussionsAdmin

Check a crypto wallet against OFAC sanctions

check_wallet_sanctions
Read-only

Check whether a crypto wallet address is on the US Treasury OFAC sanctions lists. Call this before paying an unknown counterparty, onboarding a wallet, or accepting funds. Covers Bitcoin, Ethereum/EVM, USDT, USDC, Tron, Litecoin, Monero, Solana and more; refreshed every 12 hours. Costs $0.002 (x402, USDC on Base).

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": {
      "address": "<address>"
    },
    "name": "check_wallet_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (any chain)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful operational context beyond them: multi-chain coverage, a 12-hour refresh cadence (so the agent can reason about staleness), and the $0.002 x402/USDC-on-Base payment requirement. It does not describe the shape of a result (e.g., whether a hit returns matched list entries or a boolean), which is the main remaining gap for a screening call.

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?

Three short sentences, front-loaded with the purpose, then the decision context, then coverage/cost/freshness details. Every sentence carries information an agent would act on; no filler.

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 one-parameter, read-only lookup with no output schema, the description covers what is checked, when to call it, chain coverage, freshness, and cost. The omission of any indication of what a positive versus negative result contains is the only material shortfall.

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% and there is a single required parameter, so the baseline is already high. The description adds that the address may come from any supported chain and enumerates those chains, which meaningfully extends the terse 'Wallet address (any chain)' schema text.

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 and resource ('Check whether a crypto wallet address is on the US Treasury OFAC sanctions lists'), naming both the subject type (wallet address) and the exact list. This clearly separates it from siblings like screen_sanctions_name (name-based) and sanctions_list_status (list metadata).

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?

Gives three concrete triggering scenarios: before paying an unknown counterparty, onboarding a wallet, or accepting funds. That is strong when-to-use guidance, though it stops short of stating exclusions or explicitly routing name-based screening to the sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Public Domain Check toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources