Skip to main content
Glama

Wallet activity profile (x402)

smart_money_wallet_activity

Read-onlyIdempotent

$0.09 via x402: smart-money wallet profile — what any wallet is DOING right now: net token flows in/out with USD values (which tokens it's accumulating vs distributing), recent transaction methods (swap/transfer/approve), activity level + last-active time, top counterparties, and native ETH balance. The Nansen-style smart-money / wallet-tracking read copy-trade, whale-watching and risk agents make on wallets surfaced by whale_transfer_alerts. Each flow chains into token_security_check and dex_token_data. Chains: base, ethereum, optimism, arbitrum, polygon. Live from Blockscout.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase|ethereum|optimism|arbitrum|polygon (default base)
walletYesWallet address to profile (0x...)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses a paid x402 call at $0.09, the supported chain set, and that results are live from Blockscout (freshness). It does not state cost-recovery behavior on failure, rate limits, or what happens when payment terms are returned, leaving some operational gaps.

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?

The price/purpose lead is front-loaded and the returns are listed compactly in one sentence. The chain list is duplicated at the end even though the schema already enumerates it, and the agent-audience framing ('agents make on wallets') is slightly ornate, but nothing is seriously wasted.

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?

There is no output schema, so the description must describe returns — and it does so thoroughly, plus it explains the payment handshake. It falls short only on edge cases an agent might hit, such as an unsupported chain or an unpaid call, but for a read-only profiling tool it is close to complete.

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 chain and wallet are already fully documented; the description mainly restates the chain list. The one genuine addition is the $0.09 price, which gives meaning to the x_payment parameter beyond 'x402 payment payload', but that is a modest increment over the schema baseline.

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?

The description names a concrete verb+resource ('smart-money wallet profile') and enumerates exactly what is returned: net token flows with USD values, recent tx methods, activity level, counterparties, ETH balance. It implicitly separates itself from wallet_portfolio ('what any wallet is DOING right now' vs holdings) but never names that sibling, so differentiation is inferred rather than stated.

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?

It gives real usage context: intended for copy-trade/whale-watching/risk agents, run on wallets surfaced by whale_transfer_alerts, and chained into token_security_check and dex_token_data. What is missing is an explicit exclusion clause (e.g., use wallet_portfolio instead when you want balances rather than activity), so the agent must infer the boundary.

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