Skip to main content
Glama

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

Crypto support ticket triage for exchange / wallet helpdesks (situation, priority, bilingual reply) ($0.040)

triage_crypto_support_ticket
Read-onlyIdempotent

For the helpdesk bots and agents of crypto exchanges, wallets and projects: one customer ticket in Chinese or English -> which of 21 common situations it is (deposit not credited, wrong network, missing memo / tag, stuck tx, bridge delay, tokens not showing, fake support DMs, address poisoning, leaked seed phrase, approval drain, phishing site, "fund recovery" scam, hacked account, no gas, ...), priority P0-P3, an honest recoverability call, the networks / coins / amounts / TxIDs / addresses found and what to ask for next, a ready reply in Chinese AND English, the internal note, a pre-filled escalation ticket and the red lines. A seed phrase or private key the customer pasted is caught and redacted (P0). Rule-based, no model. $0.04 a ticket. PAID: $0.040 per call or 40 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/support-ticket-triage.

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": {
      "ticket": "<ticket>"
    },
    "name": "triage_crypto_support_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWhich reply language is primary (both are always returned). auto = the ticket's language.
ticketYesThe customer's support message (Chinese or English, max 2500 characters). "text" and "message" are accepted as aliases.
platform_nameNoOptional: your exchange / wallet / project name, filled into the reply (max 60 characters).
official_domainsNoOptional: your official domains, comma-separated (max 10). Look-alikes in the ticket are flagged and the first one fills [official URL].
official_addressesNoOptional: your official contract / deposit addresses, comma-separated (max 20). Look-alike addresses in the ticket are flagged.
supported_networksNoOptional: networks your platform accepts deposits on, comma-separated (ethereum, tron, bsc, arbitrum, optimism, base, polygon, solana, avalanche, ton, bitcoin, xrp; ERC20 / TRC20 / BEP20 work too). Decides the wrong-network reply automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 substantial behavior beyond them: rule-based with no model, pasted seed phrases or private keys are caught and redacted as P0, unpaid calls return payment terms and charge nothing, bad input is rejected before payment, and failed work is never charged. These are exactly the operational traits an agent cannot get from the annotations.

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 core purpose is front-loaded, but the opening sentence is a very long chain of parenthetical enumerations, and roughly a third of the text is pricing and payment-mechanics boilerplate that repeats itself ('$0.040' appears three times). It is organized but not tight; trimming the situation list and consolidating payment terms would improve it.

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 the necessary work of describing the return payload field by field, plus payment and error semantics. The only gap is that it never says what format the response takes (JSON shape, field names) or what the escalation ticket payload looks like beyond 'pre-filled', which leaves a caller guessing about structure.

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 every parameter including lang, platform_name, official_domains, official_addresses and supported_networks is already documented in the schema, including enum values and look-alike flagging. The description adds only the general claim that networks/coins/amounts/TxIDs/addresses are extracted, not parameter-specific meaning, so the baseline 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 concrete verb and resource ('triage one customer ticket') and enumerates the exact outputs: one of 21 situations, P0-P3 priority, recoverability call, extracted entities, bilingual reply, internal note, escalation ticket. The enumeration of situations (deposit not credited, wrong network, missing memo, address poisoning, leaked seed phrase...) makes it unmistakably distinct from the sibling scam-detection and address-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?

Names the audience and unit of work ('helpdesk bots and agents of crypto exchanges, wallets and projects: one customer ticket'), which sets a clear context for use, and routes payment setup to credits_quote / credits_claim explicitly. It stops short of stating when a caller should use this instead of check_crypto_chat_message_for_scams or detect_address_poisoning_lookalike, so the sibling boundary is left implicit.

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