Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

Wallet screening: is this address on the OFAC sanctions list or a known scam/drainer list?

wallet_sanctions_check
Read-only

Screens 1 to 20 wallet addresses against the US Treasury OFAC SDN sanctions list (crypto addresses) and the ScamSniffer scam and drainer blacklist, in one call at one price. Returns block or clear per address with the reason, plus list sizes and freshness. Address-level, so it works for Base, Arc, Ethereum and any EVM chain. Useful before sending a payment, paying an x402 seller, accepting funds, or approving a spender. Read-only. Not charged for invalid addresses. Paid via x402; see list_prices.

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": {
      "addresses": "<addresses>"
    },
    "name": "wallet_sanctions_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYes1 to 20 wallet 0x addresses (an array, or one comma-separated string).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only and open-world behavior, but the description adds important operational context: one call at one price, x402 payment, no charge for invalid addresses, and return values of block/clear with reason plus list sizes and freshness. This goes well beyond what the annotations provide.

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 description is front-loaded, scannable, and dense with decision-relevant information. Every sentence contributes something useful about scope, usage, pricing, or return behavior.

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, yet the description explains that results are block or clear per address with reason, plus list sizes and freshness. Combined with input limits, chain coverage, and payment details, it is complete enough for an agent to call the tool correctly.

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 schema already documents the addresses parameter, including the 1-to-20 range and array/comma-separated string format. The description reinforces the address count and EVM-chain applicability but adds no new syntax or constraints beyond the schema.

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 names a specific verb (screens), resource (1 to 20 wallet addresses), and concrete external lists (OFAC SDN and ScamSniffer). It clearly distinguishes this from sibling tools like token_safety_check by being address-level rather than token-level.

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 clear usage contexts: before sending a payment, paying an x402 seller, accepting funds, or approving a spender. It does not explicitly name alternatives or when-not-to-use cases, but the purpose and address-level scope make the appropriate use case clear.

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

All VerifyLite 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