Skip to main content
Glama

Sanctions check

sanctions_check
Read-onlyIdempotent

Sanctions check for a wallet on any chain: OFAC SDN listing from Treasury's official list (entry, programs, list date), plus USDC and USDT freeze status on chain for 0x addresses. A screen of public lists, not legal advice. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
addressYeswallet address on any chain
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations by disclosing data provenance (Treasury's official SDN list, on-chain freeze status), the exact return fields (entry, programs, list date), a legal disclaimer, and the price and payment mechanics ($0.002 per call, accepted assets and chains). Annotations already cover read-only/idempotent, and the description adds the commercial and authorization context an agent needs.

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?

Three dense sentences, front-loaded with purpose and ending with the payment procedure. Every sentence carries information, though the pricing parenthetical is slightly heavy and the description could be broken into clearer steps.

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 two-parameter, no-output-schema tool, the definition covers what is checked, what comes back, the cost, the two-step auth flow, and the legal caveat. An agent has everything needed to invoke it correctly on the first or second call.

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%, so the baseline is 3, but the description adds real meaning beyond the schema for `payment`: it explains that the first call returns terms and the second call with a signed payload completes the purchase inside the tool call. That sequencing is not derivable from the schema alone.

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 ('Sanctions check for a wallet on any chain') and enumerates exactly what is screened: OFAC SDN entry, programs, list date, plus USDC/USDT freeze status on chain. No sibling tool covers sanctions screening, and the description makes that scope unambiguous.

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 explicit operational guidance for the x402 flow: call once without `payment` to get terms, sign them with your own wallet, call again with `payment`. It also scopes applicability to 0x addresses for the freeze check. What it does not do is name an alternative or exclusion case, but no sibling overlaps this function.

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