Skip to main content
Glama

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

Payout pre-flight: screen a whole recipient list before a batch payment ($0.050)

screen_payout_recipient_list
Read-onlyIdempotent

Before payroll, bounty / grant / contributor payouts, airdrops or refunds: up to 200 recipients (optionally with amounts) in ONE call. Per row: format, checksum, network, token-contract / burn addresses, pasted tx hashes or keys, OFAC SDN exact match. Whole list: duplicates (paid twice), look-alike pairs (address poisoning or typos), look-alikes of addresses you trust. Returns the rows to pay, the rows to hold and totals. PAID: $0.050 per call or 50 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/payout-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": {
      "recipients": "<recipients>"
    },
    "name": "screen_payout_recipient_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
knownNoOptional: up to 50 addresses you already trust (comma-separated); rows that imitate one of them are held.
networkNoNetwork you will pay on (base, ethereum, arbitrum, tron, solana, bitcoin, ...). Every row is checked against it. Omit to check formats only.
recipientsYesUp to 200 recipients: "address" or "address:amount", separated by commas or new lines (CSV "address,amount" lines and a JSON array of {address, amount} also work). Amounts are plain decimals in any unit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial behavioral context the annotations cannot carry: pricing ($0.050 or 50 credits), payment mechanics (x402 over MCP, credits key via Bearer header), and failure semantics — unpaid calls return terms and charge nothing, bad input is rejected before payment, failed work is never charged. It also states what comes back (rows to pay, rows to hold, totals).

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?

It is front-loaded with the trigger and scope, then the per-row/per-list checks, then returns, then payment — a sensible order. The payment paragraph is long and slightly dense, but each sentence carries information an agent needs to actually complete a paid call, so waste is minimal.

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 takes on the burden of describing returns, and it does ('the rows to pay, the rows to hold and totals'). Combined with billing behavior, error handling and a pointer to the equivalent REST endpoint, an agent has everything needed to invoke this 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 description coverage is 100%, so the schema already documents recipients, network and known in detail. The description's parameter-relevant content ('up to 200 recipients, optionally with amounts', 'look-alikes of addresses you trust') largely restates the schema rather than adding syntax, format or edge-case meaning. Baseline 3 is appropriate.

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 and resource ('screen a whole recipient list before a batch payment') and scopes it precisely ('up to 200 recipients ... in ONE call'), which immediately separates it from the single-address siblings like check_crypto_address_before_sending. It also enumerates the checks performed per row and per list, so an agent knows exactly what class of operation this is.

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 opening clause gives concrete when-to-use triggers: payroll, bounty/grant/contributor payouts, airdrops, refunds. It implies the when-not by emphasizing 'whole list' and 'ONE call', steering single-address checks elsewhere, though it never names an alternative tool explicitly. Clear context, but no explicit exclusion or sibling routing.

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