Skip to main content
Glama
Sign In

Finch Agent Catalog

by io.github.a0971025732-netizen
OverviewDiscussionsAdmin

Check crypto address against OFAC sanctions

check_crypto_address_sanctions
Read-only

Free, no-auth check of a crypto wallet address (BTC, ETH, TRX, USDT, LTC, XMR and more) against the US Treasury OFAC SDN sanctions list. Returns whether the address is listed, the sanctioned party and program, and the list date. For fund-flow tracing of any address, it points to MistTrack by SlowMist on Finch.

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

Input Schema

NameRequiredDescriptionDefault
addressYesThe wallet address to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Adds context beyond the readOnlyHint/openWorldHint annotations: it is free, requires no auth, covers a named chain list, and returns listing status, sanctioned party/program and list date. Rate limits, error behavior for unsupported chains, and freshness of the SDN data are not disclosed.

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?

Two sentences, front-loaded with what is checked and the free/no-auth property, then the return fields, then the alternative. Slightly promotional mention of a third-party product is minor but does earn its place as a routing hint.

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 one-parameter read tool with annotations and no output schema, the description covers what it returns (is-listed, party, program, list date) and its auth/cost profile. Missing only edge-case behavior such as unsupported or malformed addresses.

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 the single `address` param is documented, so the baseline is 3. The description adds that the address may belong to any of several chains and no chain parameter is needed, but gives no format or validation guidance.

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 (check a crypto wallet address against OFAC SDN), plus the supported chains and the exact fields returned. It is clearly distinguishable from siblings like trace_crypto_funds and check_wallet_address_risk.

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 clear context ('Free, no-auth check') and explicitly redirects fund-flow tracing to MistTrack by SlowMist on Finch, which implies when not to use this tool. It stops short of naming the exact sibling tools or stating exclusions for risk-scoring use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Finch Agent Catalog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources