Skip to main content
Glama

wallet risk

wallet-risk
Read-onlyIdempotent

Wallet risk verdict from OFAC SDN mirror + ScamSniffer scam-database + GoPlus malicious-address DB + explorer profile -> ALLOW/REVIEW/BLOCK, every flag with provenance Price: $0.05 per call, USDC on Base via x402.

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": {
      "address": "<address>"
    },
    "name": "wallet-risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNooptional: base (default)|ethereum|optimism|arbitrum|gnosis
addressYes0x... (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"base|ethereum|optimism|arbitrum|gnosis"New value: +"optional: base (default)|ethereum|optimism|arbitrum|gnosis"
    • changedInput schema / required
      Previous value: -[
      -  "address",
      -  "chain"
      -]New value: +[
      +  "address"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, and the description adds information the annotations cannot convey: the upstream sources queried, that every flag carries provenance, and that a call costs $0.05 in USDC on Base via x402. It does not address latency, caching, rate limits, or failure behavior when an upstream source is unavailable.

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

Conciseness5/5

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

Two compact statements: first the verdict, sources, and output shape, then the pricing and payment rail. Every fragment carries information and the most decision-relevant content (what it returns, what it costs) is front-loaded.

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 only two parameters and no output schema, the description usefully characterizes the response (ALLOW/REVIEW/BLOCK plus per-flag provenance) and discloses the payment requirement. The main gap is the absence of any threshold semantics — what distinguishes REVIEW from BLOCK — which an agent would want before acting on the verdict.

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%, and the schema already lists the chain enum values including base as default and marks address as required. The description adds no meaning beyond that — it never explains address format assumptions, chain-defaulting behavior, or what a mismatched chain does to the verdict. Baseline 3 applies when the schema does the documentation work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Wallet risk verdict" names a specific resource (a wallet address) and operation (risk verdict), and the description enumerates the four data sources and the three possible outcomes. It stops short of distinguishing itself from the sibling token-check / token-check-free tools, so the agent must infer that this one screens addresses rather than tokens.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the described inputs and outputs — the agent can infer this is the tool for screening an address against sanctions/scam lists. There is no explicit when-to-use or when-not statement and no named alternative (e.g., the free or token-oriented siblings), leaving the exclusion decision to the caller.

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