Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

check_sanctions

Read-onlyIdempotent

chainpeek: screen one crypto address against the US OFAC SDN list's digital currency addresses. For up to 1,000 addresses use check_sanctions_batch; for lookalikes use check_address_poisoning. EVM and bech32 addresses match case-insensitively; base58 BTC, TRX and other formats must match exactly as listed. Screening against the US OFAC SDN digital-currency-address list only (the Treasury SDN list's published crypto addresses), as of the list_date in the answer; a non-match does not clear an address; not legal advice or a full compliance check (no other sanctions lists, no clustering, ownership or exposure analysis); verify any match at sanctionssearch.ofac.treas.gov. Local lookup, typically under 0.1 s (first call up to 1 s). Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/check-crypto-address-sanctions.html

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_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesCrypto address: EVM 0x address, bech32, or a BTC/TRX/other address exactly as listed.

Output Schema

NameRequiredDescriptionDefault
listNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
sourceNo
addressNo
matchedNo
matchesNo
list_dateNo
disclaimerNo
address_kindNo
list_addressesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / address / title
      Removed value: -"Address"
    • removedInput schema / title
      Removed value: -"check_sanctionsArguments"
    • removedOutput schema / properties / matches / items
      Removed value: -{
      -  "properties": {
      -    "currency": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "listed_address": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "programs": {
      -      "items": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "type": [
      -        "array",
      -        "null"
      -      ]
      -    },
      -    "sdn_name": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "sdn_type": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "sdn_uid": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "address": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "address_kind": {
      +      "enum": [
      +        "evm",
      +        "bech32",
      +        "other",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "disclaimer": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "list": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "list_addresses": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "list_date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "matched": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "matches": {
      +      "items": {
      +        "properties": {
      +          "currency": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "listed_address": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "programs": {
      +            "items": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "type": [
      +              "array",
      +              "null"
      +            ]
      +          },
      +          "sdn_name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "sdn_type": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "sdn_uid": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations, which already cover readOnly/idempotent/destructive/openWorld. It discloses latency profile (typically <0.1 s, first call up to 1 s), pricing (USD 0.002), the free tier (10 reads per IP per UTC day), the snapshot nature of the data (as of list_date), that non-matches do not clear an address, and a verification path at sanctionssearch.ofac.treas.gov. That is unusually complete behavioral disclosure for a screening tool.

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?

Purpose is front-loaded in the first clause and every subsequent sentence carries operational weight (routing, matching rules, caveats, cost, docs link). It is a dense block rather than a scannable structure, and the price/free-tier/doc-link tail could be trimmed, but little is genuinely wasted.

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?

An output schema exists, so return-value explanation is not required. For a single-parameter screening tool, the description covers scope, limits, alternatives, matching rules, timing, cost and disclaimers — nothing an agent needs to invoke it correctly is missing.

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?

Only one parameter with 100% schema coverage, so baseline is high; the description still adds real meaning by spelling out matching semantics per format — EVM and bech32 match case-insensitively while base58 BTC, TRX and other formats must match exactly. The schema description only hints at 'exactly as listed', so this clarifies rather than repeats.

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?

Opens with a specific verb and resource: 'screen one crypto address against the US OFAC SDN list's digital currency addresses.' The word 'one' plus the explicit routing to check_sanctions_batch and check_address_poisoning makes it distinguishable from siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use-else guidance: batch for up to 1,000 addresses, check_address_poisoning for lookalikes. It also states the boundary conditions of the tool's scope (only OFAC SDN crypto addresses, no other lists, no ownership/exposure analysis) and what a non-match means, which is what an agent needs to decide to call it at all.

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.