Skip to main content
Glama

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

Moderation sweep: scam-check up to 25 chat messages from one group at once ($0.050)

sweep_crypto_chat_messages_for_scams
Read-onlyIdempotent

For moderation bots and support desks clearing a backlog (back-scan a Telegram / Discord group when your bot joins, sweep a moderation queue): up to 25 messages, each with the full single-message analysis (phishing domains, brand look-alikes, scam scripts in English and Chinese, leaked keys redacted). Plus: campaigns (the same bad host, fake brand or scam script across messages and senders), per-sender recommendation (ban_candidate / mute_and_review / watch), the ids to remove / hold / warn, and ONE pinned group warning in Chinese and English. $0.002 a message instead of $0.003. 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/scam-message-batch.

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": {
      "messages": "<messages>"
    },
    "name": "sweep_crypto_chat_messages_for_scams"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNocompact (default): per-message verdict, action, hosts, signal codes and summary. full: also the complete per-message report (links, findings, replies).
messagesYesUp to 25 chat messages from one chat. Each item: {"id": "optional", "from": "optional sender", "text": "the message"}.
official_domainsNoOptional: your project's own domains, comma-separated (max 10). Confirmed as official; look-alikes of them are flagged.
official_addressesNoOptional: your official contract / treasury / deposit addresses, comma-separated (max 20). Addresses in the messages that imitate them are flagged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the bar is lower, yet the description still adds substantive behavior: pricing ($0.002/message, $0.050 per call or 50 credits), payment paths (x402 over MCP, or credits_quote/credits_claim with a Bearer key), and crucially the failure semantics — unpaid calls return terms and charge nothing, bad input is rejected pre-payment, failed work is never charged.

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?

The use case is front-loaded and the scope constraint appears early, which is good. But the body is a dense run-on parenthetical stacking pricing, payment rails, and billing guarantees into one sentence, and the cost figures are restated twice ($0.050 / 50 credits and $0.002 vs $0.003), which spends words without adding selection value.

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, so the description carries the return-value burden and does so thoroughly: per-message verdicts, campaign clustering across senders, a per-sender ban/mute/watch recommendation, the ids to remove/hold/warn, and one pinned bilingual group warning. For a paid, multi-message moderation tool, an agent has everything needed to decide and invoke 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%, so every parameter is already documented, making 3 the baseline. The description adds meaning about outputs (full vs. summary-level per-message analysis, the pinned bilingual warning) but says nothing extra about official_domains or official_addresses beyond what the schema states, so it does not clear the baseline.

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 action and scope: scam-check up to 25 chat messages from a single group, returning full per-message analysis plus campaign-level rollups. The batch scope itself separates it from the single-message sibling check_crypto_chat_message_for_scams, and the reference to 'GET /v1/scam-message-batch' anchors it to a concrete operation.

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?

Gives concrete trigger contexts — a moderation bot back-scanning a group on join, or a support desk sweeping a queue — which tells the agent when this is the right call. It stops short of an explicit when-not or of naming the single-message tool as the alternative for one-off checks, relying on the reader to infer the split from 'up to 25'.

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