Skip to main content
Glama

Base Agent Due-Diligence Kit

Wallet X-Ray ($0.005)

wallet_xray
Read-onlyIdempotent

Wallet risk check / address reputation for any Base address before you pay it or get paid by it: wallet age, balances, USDC in/out flows, x402-style (EIP-3009) payment history, wash-trading (round-trip) and self-funded-traction (concentration) flags, 0-100 score and verdict. Free teaser at /v1/wallet-xray/peek. Descriptive statistics of public chain data, not financial advice. PAID: $0.005 per call in USDC on Base via x402, or use a 0.25 USDC transfer pass (pay_tx). See payment_options. By Dex.

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_xray"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoLook-back window for USDC flows in hours (1-72, default 12)
pay_txNoOptional, for the plain-transfer option (no x402 needed): hash of a USDC transfer of >= 0.25 USDC to this server's receiving address (get it from the payment_options tool). One transfer unlocks every paid tool for 24h.
addressYesBase address to profile (wallet or contract)
pay_chainNoChain of pay_tx (default: inferred; 0x hash = base, base58 signature = solana)

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 readOnly/idempotent/non-destructive, but the description adds the critical behavioral facts those annotations cannot: the $0.005 USDC-on-Base price, the x402 flow, the alternative 0.25 USDC transfer pass via pay_tx that unlocks all paid tools for 24h, and a disclaimer that output is descriptive statistics not advice. Payment gating is the single most important behavior for an agent to know before calling, and it is fully disclosed.

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

Conciseness4/5

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

Purpose and audience are front-loaded in the first clause, then the feature list, then payment mechanics and the disclaimer. It is dense and slightly run-on with the price repeated in both title and body, but every sentence carries usable information.

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 carries the return-value burden and does so by naming the specific fields and the 0-100 score/verdict. Payment and attribution are covered; the only remaining gap is the response envelope shape (e.g., raw JSON structure or pagination), which for a single-address profile tool is minor.

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 the schema already documents address, hours, pay_tx, and pay_chain. The description reinforces the payment workflow (transfer pass, payment_options) which contextualizes pay_tx, but adds no syntax or range detail beyond the schema, 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+resource ("wallet risk check / address reputation for any Base address") and enumerates exactly what is profiled: wallet age, balances, USDC flows, EIP-3009 payment history, wash-trading and concentration flags, 0-100 score and verdict. It also implicitly separates itself from wallet_xray_peek by naming the free teaser endpoint, so an agent can distinguish paid vs. free variants.

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 a clear triggering condition ("before you pay it or get paid by it"), which is exactly the decision point an agent needs. It also points to the free teaser and to payment_options for the paid path, but never states when NOT to use it (e.g., non-Base addresses, contract profiling where contract_xray is the better fit).

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