Skip to main content
Glama

Ellimist

OFAC SDN wallet lookup

data_risk_ofac
Read-only

Use this to check whether a crypto wallet address is sanctioned: matches it against digital currency addresses on the official U.S. Treasury OFAC SDN list (KYC/AML screening, compliance). Price: $0.005 USDC per call via x402 (no account). Not charged if it fails.

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

Input Schema

NameRequiredDescriptionDefault
atNoPast point in time (UTC) to check instead of today: proves whether the address was listed then, from Ellimist's list history
addressYes

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 and openWorldHint, so the read-only nature is covered. The description adds real value beyond them by disclosing the payment model: $0.005 USDC per call via x402, no account required, and no charge on failure, which matters for an agent deciding whether to call it. It stops short of describing the shape of a match result, which is a meaningful omission given there is no output schema.

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?

Two sentences, front-loaded with the purpose and followed by the cost/charging caveat. Every clause carries information an agent needs; nothing is padded.

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 single-address screening lookup with no output schema, the definition covers the what, the why, and the billing behavior. The remaining gap is return-value shape (match/no-match, SDN entry details) and chain scope, which an agent would want but is not crippling for a boolean-style check.

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?

With 50% schema coverage, the 'at' parameter is already documented in the schema as a historical point-in-time check, and the description adds nothing further about it. For the undocumented 'address' parameter the description does clarify it is a crypto wallet address, but leaves the chain/format ambiguity unresolved (the schema only constrains it as a non-whitespace string up to 128 chars). Net, it partially compensates for the coverage gap.

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 description states a specific verb and resource: check whether a crypto wallet address is sanctioned by matching it against digital currency addresses on the OFAC SDN list. That is instantly distinguishable from every listed sibling, none of which do sanctions screening.

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 names the concrete use cases (KYC/AML screening, compliance) so an agent knows the context in which to reach for it. It does not state when not to use it or name an alternative tool, which keeps it out of the top band.

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