Skip to main content
Glama

Check Before Signing or Sending (Crypto)

crypto_check_before_sign
Read-onlyIdempotent

Before an agent signs or sends from a crypto wallet: send the destination address (to), the page that asked (url) and/or the wallet request it is about to approve (request: the EIP-1193 method and params). The address is checked for its chain and checksum, the US Treasury OFAC sanctions list, the addresses the FBI published in its alerts, whether Tether froze USDT at it, and pages DechoNet judged dangerous that showed it; the page goes through the phishing link check and the official exchange, wallet and dApp list; the request is read for what approving it would allow (unlimited token approval, approval for a whole NFT collection, Permit/Permit2 signatures, Seaport orders, raw eth_sign, transfers). Verdicts: danger, suspicious, no_signals. no_signals means none of the checks found a warning sign and is not a statement that the transaction is harmless; 'unchecked' lists what was not looked at (balances, token contracts, simulation). Nothing sent is stored. Rate-limited.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_check_before_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDestination wallet address (0x…, T…, bc1…, Solana)
urlNoAddress of the page that asked for the signature or transfer (https://…)
requestNoThe wallet request about to be approved

Output Schema

NameRequiredDescriptionDefault
requestNoWhat approving the request would allow
signalsYes
verdictYesdanger: a check found a danger sign; suspicious: a warning sign; no_signals: none of the checks found one — not a statement that the transaction is harmless (see unchecked)
receiptsNoSigned observation receipts behind this result, one per lookup: when, from where and under which rules version DechoNet observed it. Each url shows the record and checks its Ed25519 signature.
uncheckedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/idempotentHint the description discloses what is actually inspected (chain and checksum, OFAC list, FBI-published addresses, Tether freezes, phishing and dApp lists, approval/eth_sign/Seaport semantics), the meaning of each verdict, that 'unchecked' enumerates skipped checks, that nothing sent is stored, and that the endpoint is rate-limited. Critically, it warns that 'no_signals' is not a safety assurance, which prevents the agent from over-reading a clean result.

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 opening clause is well front-loaded and little here is filler, but the central sentence is a long semicolon-chained run-on that crams five address sources, two page sources and six request patterns into one breath. The information earns its place; the packaging makes it harder to parse than necessary.

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?

For a multi-source, nested-object tool with an output schema, the description covers the safety profile, verdict semantics, provenance limits and side effects. The remaining gap is that the schema marks zero required parameters, yet the description never says whether at least one of to/url/request must be supplied or what happens if all are absent.

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 baseline is 3, but the description adds the purpose of each argument: 'to' is what gets chain/checksum/sanctions scrutiny, 'url' is what enters the phishing and dApp list checks, and 'request' is 'read for what approving it would allow' with concrete examples of the risky method shapes. It stops short of noting that all three parameters are optional and how the check behaves when one is omitted.

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?

Names a specific verb and resource ('check the destination address, page and wallet request before an agent signs or sends'), and enumerates the exact evidence sources consulted, which separates it cleanly from siblings like wallet_address_check, phishing_link_check and crypto_exchange_check. The verdict vocabulary (danger/suspicious/no_signals) further pins down what the tool returns.

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 triggering condition is explicit and front-loaded: 'Before an agent signs or sends from a crypto wallet'. It also states the inputs to supply in that situation. It does not, however, route the agent to alternatives (e.g. wallet_address_check for a bare address with no request, or crypto_exchange_check for counterparty vetting), so the when-not guidance is implied rather than stated.

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