ScrapeMole Onchain

ScrapeMole Onchain: prices, DEX prices, ENS/Basenames, gas, tokens, balances, holders and transactions on Base and Ethereum: Wallet balances

balances

Read-onlyIdempotent

Use when you need what a wallet or contract holds: reads the native ETH balance and ERC-20 balances (a default set of major tokens, or up to 20 token symbols/addresses you pass) for one address on Base or Ethereum in a single multicall, with human-readable amounts and USD values from Chainlink feeds, plus a total. Zero balances are omitted unless asked. Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.

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": "balances"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Chain.	base
`tokens`	No	Comma-separated token symbols (from the default list) or 0x token addresses, max 20. Default: major tokens of the chain.
`address`	Yes	Wallet or contract address (0x…).
`includeZero`	No	Also list zero balances (true/false).	false

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the multicall execution model, Chainlink price sourcing, the zero-balance omission default, and — critically — the paid x402 USDC model at $0.003 per successful call with the unpaid PaymentRequired response. That payment/auth behavior cannot be inferred from annotations or schema and is exactly what an agent needs before invoking.

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 usage trigger is front-loaded and the single long sentence packs purpose, scope, return shape, and defaults without filler; the payment sentence is separated for emphasis. It is dense but every clause carries information, with only mild redundancy against the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by describing the return shape (human-readable amounts, USD values from Chainlink, plus a total) and the omission rule for zero balances. Combined with explicit payment semantics, an agent has everything needed to call and interpret this tool.

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 real meaning: the tokens parameter defaults to a chain-specific major-token set versus up to 20 symbols/addresses, and includeZero's default omission behavior is stated explicitly rather than implied by a "false" default.

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 and resource — reads native ETH and ERC-20 balances for one address on Base or Ethereum — and adds scope details (multicall, default token set, USD values, total). This clearly distinguishes it from siblings like holders, tx, token, and price, which cover different resources.

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?

"Use when you need what a wallet or contract holds" gives explicit context for selecting this tool, and the zero-balance behavior narrows it further. It does not name alternatives (e.g. use holders for token holder lists, token for metadata), so routing between siblings is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScrapeMole Onchain tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?