Skip to main content
Glama

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

Scam check for one crypto chat message (Telegram / Discord moderation, support inbox) ($0.003)

check_crypto_chat_message_for_scams
Read-onlyIdempotent

For community moderation bots and support desks: every link (known crypto-phishing domain list, brand look-alikes of ~90 wallets / exchanges / DeFi apps, homoglyph / punycode, typo-squats, free-hosting drainer pages, shorteners), scam scripts in English and Chinese (seed-phrase requests, fake support DMs, wallet "validation", fund recovery, giveaways, airdrop bait), and secrets the sender leaked (returned redacted). Returns allow / review / block, an action and a ready-to-post moderator reply in Chinese and English. PAID: $0.003 per call or 3 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/scam-message-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": {
      "text": "<text>"
    },
    "name": "check_crypto_chat_message_for_scams"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe chat message to check (max 4000 characters). "message" is accepted as an alias.
official_domainsNoOptional: your project's own domains, comma-separated (max 10). They are confirmed as official and look-alikes of them are flagged.
official_addressesNoOptional: your official contract / treasury / deposit addresses, comma-separated (max 20). Addresses in the message that imitate them are flagged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: cost ($0.003 or 3 credits), that unpaid calls return payment terms and charge nothing, that invalid input is rejected before any charge, that failed work is never charged, and that leaked secrets are returned redacted. These are exactly the billing and safety details an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the body is a single dense block mixing detection capabilities, return values, and three separate payment mechanics with nested parentheticals, which is hard to scan. Nearly every clause is substantive, yet the payment and detection sections would be clearer as separated sentences or a short list.

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?

With no output schema, the description does carry the return contract and does so reasonably: verdict values (allow / review / block), an action, a ready-to-post moderator reply in Chinese and English, and redacted secrets. It is complete on payment and failure modes; the main residual gap is the exact response field structure an agent must parse.

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 both optional parameters are already fully documented, including the 4000-character limit, comma-separated format, and max counts. The description does not add syntax or format meaning beyond that, so the baseline of 3 applies.

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 one crypto chat message for scams') and enumerates the concrete detection classes: known phishing domains, brand look-alikes, homoglyph/punycode, typo-squats, drainer pages, shorteners, scam scripts in EN/ZH, and leaked secrets. The singular 'one message' framing plus the moderation/support-desk scope makes it distinguishable from the batch-oriented sibling.

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 names the intended contexts (community moderation bots, support desks), and the description gives explicit payment preconditions: use x402 over MCP, or buy credits via credits_quote / credits_claim then send 'Authorization: Bearer ssk_...'. It also states the alternative access path (GET /v1/scam-message-check). What it lacks is explicit when-not guidance, e.g. when to batch with sweep_crypto_chat_messages_for_scams instead of single-message checking.

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