Skip to main content
Glama

Safe-Send Check: crypto support triage, sanctions and scam screening

Pre-transfer address check (format, checksum, network, memo) ($0.001)

check_crypto_address_before_sending
Read-onlyIdempotent

Before sending crypto: detects the chain family (EVM, TRON, Bitcoin, Litecoin, Dogecoin, Solana, TON, XRP), verifies checksums, catches token-contract / burn addresses as recipients, invisible or look-alike characters, pasted tx hashes or private keys, testnet addresses and address / network mismatches (e.g. a 0x address on TRC-20); flags a missing memo / tag for exchange deposits. Verdict ok / caution / incomplete / do_not_send. PAID: $0.001 per call or 1 prepaid credits, no account. Pay with x402 over MCP (USDC on Base), or with a credits key bought by a plain USDC transfer (credits_quote / credits_claim, then header Authorization: Bearer ssk_...). An unpaid call returns the payment terms and charges nothing; bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/address-check.

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

Input Schema

NameRequiredDescriptionDefault
memoNoMemo / destination tag you plan to include (TON, XRP, XLM, ...; max 100 chars)
addressYesDestination address to check (max 200 chars)
networkNoNetwork you intend to send on. Aliases accepted: ethereum, arbitrum, optimism, bnb, trc20, solana, bitcoin, eip155:<id>. Omit to check format only.
recipientNoWho receives: exchange deposit address, your own wallet, or someone else

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them on the dimension that matters most here: the paid-call contract. It states that unpaid calls return terms and charge nothing, bad input is rejected before payment, and failed work is never charged, plus the two payment paths (x402 or credits key).

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-loaded with the detection scope, then verdict values, then payment terms — a sensible ordering. The payment/billing sentences are dense and long, but each carries information the agent needs before calling a paid tool, so little is genuinely wasted.

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?

With no output schema, the description supplies the return vocabulary (ok / caution / incomplete / do_not_send), the billing behavior, and the error handling, which is everything an agent needs before invoking a read-only check. For a 4-parameter read-only tool, nothing material is missing.

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%, so the schema already carries the parameter meanings; the description nonetheless adds interpretation by naming concrete failure pairs ('a 0x address on TRC-20') and explaining what the memo field is for (exchange deposit tags) rather than just its type. That is meaningful context beyond the schema, though not a full walkthrough of all four parameters.

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?

Opens with an explicit verb and resource ('Before sending crypto: detects the chain family ... verifies checksums, catches ...'). It enumerates the specific failure classes it catches (burn addresses, look-alike characters, testnet addresses, address/network mismatch), which makes it unmistakable against the sibling scam/OFAC screening tools.

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?

The trigger condition is clear and front-loaded ('Before sending crypto'), and it specifies a scope control ('Omit to check format only') plus a deposit-specific case (missing memo/tag for exchange deposits). It does not explicitly say when to prefer the sibling address tools such as detect_address_poisoning_lookalike or screen_wallet_ofac_sanctions, so routing between them is left to inference.

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