ScrapeMole Onchain

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

price

Read-onlyIdempotent

Use when you need a trustworthy USD price for crypto assets (ETH, BTC, cbBTC, SOL, LINK, AAVE, stablecoins), fiat FX rates (EUR, GBP, JPY…) or metals (XAU, XAG): reads the Chainlink price feed contracts directly from Base or Ethereum in one multicall and returns price, last update time, age in seconds, a stale flag and the feed address so the value is verifiable on-chain. Up to 10 symbols per call. Paid tool: x402 USDC on Base, $0.002 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": {
      "symbols": "<symbols>"
    },
    "name": "price"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Chain to read the feeds from.	base
`symbols`	Yes	Comma-separated asset symbols (max 10), e.g. "ETH,BTC,USDC,EUR". GET / lists all supported symbols per chain.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With annotations only covering read-only/idempotent/open-world, the description carries the rest: it discloses batching via multicall, the exact return fields (price, last update time, age in seconds, stale flag, feed address), the 10-symbol cap, and the paid x402 USDC model at $0.002 per successful call including the PaymentRequired response when unpaid.

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?

Front-loads the trigger and the value proposition, then packs scope, return shape, limits, and cost into two dense sentences with no filler. Nothing is repeated from the schema or annotations.

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?

There is no output schema, yet the description enumerates the return fields and the stale-flag semantics, and it explains the payment failure path. For a two-parameter read tool this is complete enough to invoke confidently.

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 10-symbol limit, the comma-separated format, and the supported symbol universe (ETH, BTC, cbBTC, SOL, LINK, AAVE, stablecoins, EUR/GBP/JPY, XAU/XAG). The chain parameter's effect is left to the schema.

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 action (reads Chainlink price feed contracts directly in one multicall) and resource (USD prices for crypto, FX rates, metals) on Base or Ethereum. The 'verifiable on-chain' oracle framing implicitly distinguishes it from the sibling dex_price, so an agent can pick correctly.

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 a trustworthy USD price for..." gives an explicit trigger, and the enumeration of asset classes (crypto, fiat FX, metals) sharpens the context. It never states when to prefer the sibling dex_price instead, so the alternative 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?