Skip to main content
Glama

Trading Signals Toolkit

OFAC Sanctions Screen

sanctions_screen
Read-only

Screen a crypto address (any chain: EVM/Base/Ethereum, Bitcoin, Tron, Solana and more, via OFAC's listed digital currency addresses) and/or a person or entity name (fuzzy, scored 0-100) against the official US Treasury OFAC SDN and Consolidated sanctions lists. Returns clear / match / possible_match, the matched entries (name, programs, aliases), list publish date, timestamp and sources. Not legal or compliance advice. Read-only, never places orders. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
nameNoPerson or entity name to screen (fuzzy match)
addressNoCrypto address on any chain, e.g. 0x… (EVM), bc1…/1…/3… (Bitcoin), T… (Tron), base58 (Solana)
minScoreNoMinimum name match score 70-100 (default 85)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive status, and the description adds real context beyond them: the three possible verdicts (clear / match / possible_match), what the matched entries contain (name, programs, aliases), the list publish date and sources, and fuzzy scoring on a 0-100 scale. It stops short of disclosing rate limits, latency, or whether results are cached, so it is strong but not complete.

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?

The operational content is a single front-loaded sentence with the resource, chains, and data source before any caveats. The trailing disclaimers are short and arguably necessary for a sanctions tool, and nothing repeats the schema verbatim.

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?

With no output schema present, the description does the work of describing return values (verdict enum, matched entries, publish date, timestamp, sources), which is the main thing an agent needs. It is close to complete, with only operational metadata like latency or result freshness left unaddressed.

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 coverage is 100% and all three parameters carry their own descriptions, including the 70-100 range and 85 default for minScore. The description only echoes that name matching is fuzzy and scored 0-100, adding no format or syntax detail beyond the schema, so the baseline of 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?

States a specific verb ("Screen") and two concrete resources (crypto address on named chains, person/entity name) and names the exact authority being checked (US Treasury OFAC SDN and Consolidated lists). This is unambiguous and clearly separable from the trading/analysis siblings.

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

Usage Guidelines3/5

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

The description implies the screening use case and says name and address are combinable via "and/or", but it gives no explicit when-to-use triggers, prerequisites, or comparison to adjacent checks in the sibling set (e.g., pre_trade_check, token_verdict). An agent can infer intent but gets no routing guidance.

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