Skip to main content
Glama
Sign In

PayGuard

by co.youraitools
OverviewDiscussionsAdmin

OFAC SDN screen of a crypto address

screen_address
Read-onlyIdempotent

Checks one crypto address against the US Treasury OFAC SDN list of sanctioned digital currency addresses (refreshed daily). For 2 or more addresses use screen_batch (up to 50 per call, counts as one call). Accepts any chain (BTC, ETH and EVM chains, TRX, SOL, LTC, XMR, BCH, XRP, ZEC and more). Free: 30 calls/day per IP with full results (max 10/min; invalid input is not counted); after that the tool returns an error with the x402 pay URL ($0.001 USDC on Base, Polygon, Arbitrum One or Solana per call at https://api.youraitools.co/payguard/v1/address) or prepaid credits. Returns sanctioned (true/false), match_count, matches[] (entity, entity_type, programs, list_date, listed_currency), address (normalized), chain {guess, format, candidates, checksum_valid}, list_updated_at and free_tier usage. Read-only; informational screening, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
addressYesOne blockchain address, e.g. "0x8589427373D6D84E98730D7795D8f6f8731FDA16" or "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh": 20-140 letters/digits, optional URI prefix such as "ethereum:" or "bitcoincash:" (stripped); EVM hex and bech32 match case-insensitively, base58 exactly. The chain is detected automatically. Any chain is accepted; the SDN list covers Bitcoin, Ethereum and other EVM chains (Base, Arbitrum, BNB Chain, Polygon...), Tron, Solana, Litecoin, Monero, Bitcoin Cash/SV/Gold, Dash, Dogecoin, Ethereum Classic, XRP, Verge, Zcash and USDT/USDC addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"Blockchain address"New value: +"One blockchain address, e.g. \"0x8589427373D6D84E98730D7795D8f6f8731FDA16\" or \"bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh\": 20-140 letters/digits, optional URI prefix such as \"ethereum:\" or \"bitcoincash:\" (stripped); EVM hex and bech32 match case-insensitively, base58 exactly. The chain is detected automatically. Any chain is accepted; the SDN list covers Bitcoin, Ethereum and other EVM chains (Base, Arbitrum, BNB Chain, Polygon...), Tron, Solana, Litecoin, Monero, Bitcoin Cash/SV/Gold, Dash, Dogecoin, Ethereum Classic, XRP, Verge, Zcash and USDT/USDC addresses."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: discloses daily list refresh, free-quota behavior, that invalid input is not counted, and exactly what happens after the quota (error with x402 pay URL, price, chains). Doesn't state whether the SDN snapshot can lag or how normalization errors surface, so not a 5.

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?

Front-loads purpose, then routing, then chain coverage, then pricing/quota, then return fields — a sensible priority order. The return-field enumeration (sanctioned, match_count, matches[] with subfields, chain object) is dense and partly verbose given there is no output schema to compensate for, but each block serves a purpose.

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?

No output schema exists, so listing the exact return fields (sanctioned, match_count, matches[] contents, normalized address, chain guess/format/candidates/checksum_valid, list_updated_at) is necessary and present. Combined with quota, pricing, and the read-only/not-legal-advice caveat, an agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 20-140 char range, URI prefixes, and case rules, so the baseline is 3. The description adds that any chain is accepted and that chain detection is automatic, which frames the parameter's scope beyond the single-address schema note, but largely repeats the chain list already present in 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?

States a specific verb and resource (checks one crypto address against the OFAC SDN list) and immediately differentiates itself from the sibling by naming screen_batch for multi-address use. An agent can distinguish scope without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes 2+ addresses to screen_batch and gives its limit (up to 50 per call, counts as one call), plus states the free-tier ceiling of 30 calls/day per IP and the 10/min rate. The when-to-use condition and the alternative are both named.

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

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