Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Sanctions check (OFAC screening): SDN screening for a crypto wallet or name

sanctions_check
Read-only

Check a crypto wallet against the OFAC SDN list before you pay it (EVM, BTC, TRX), or screen a person or company name, with aliases, against OFAC, the EU consolidated list, the UN Security Council list and the UK Sanctions List in one call. Returns a verdict (block, review, pass), each match with list, list ID, programme and strength, and every list's date. Screening aid, not legal advice. Use before paying; with wallet risk: check_counterparty. Example: address=0x098B716B8Aaf21512996dC57EB0615e2383E2f96. Price $0.009/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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; matches when every word appears in a listed name or alias
listsNoLists for a name: all (default), or any of ofac, eu, un, uk, comma-separated. Addresses are checked against OFAC, the only list that publishes crypto addresses
addressNoCrypto address to check against OFAC (give address, name or both)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds real value beyond them: pricing ($0.009/call, first 25 free, failed calls free), the explicit note that repeats are charged and therefore not free, and the 'screening aid, not legal advice' caveat — all of which explain the idempotentHint=false annotation in practical terms.

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 core purpose, list coverage and verdict are front-loaded in the first sentence, with example, pricing and the legal caveat following in a logical order. It is a dense single block with some pricing detail that could be trimmed, but nothing is wasted or buried.

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?

There is no output schema, so the description carries the return-value burden itself, and it does: verdict categories, per-match fields (list, list ID, programme, strength) and list dates. Combined with the zero-required-parameter flexibility and pricing model, an agent has everything needed to call and interpret it.

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% and the schema already explains name matching, list selection and that addresses are OFAC-only. The description adds only the alias nuance and a concrete example address format, which is useful but marginal over the schema, so the 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?

The first sentence names specific verbs and resources: check a crypto wallet against the OFAC SDN list (EVM, BTC, TRX) or screen a person/company name against OFAC, EU, UN and UK lists. It also names the return artifact (block/review/pass verdict with match details), so the tool is distinguishable from generic screening siblings.

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?

It gives an explicit timing rule ('Use before paying') and routes a related case to a sibling ('with wallet risk: check_counterparty'). It does not state when-not to use it (e.g., when a full compliance workflow or an invoice-level check is needed), so guidance is strong but not exhaustive.

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.