Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Wallet profile ($0.005)

wallet_profile
Read-only

PAID $0.005 USDC. Who is this wallet: label exchange / whale / active_trader / fresh_wallet / dormant, 0-100 activity score with reasons, native + USDC balance, tx count, first/last activity, exchange label and whale transfer history. Chains ethereum, base, solana. Computed from raw chain RPC.

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

Input Schema

NameRequiredDescriptionDefault
chainNo
addressYesWallet address
api_keyNoOptional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional prepaid key (sk_scrapling_...). Otherwise pay per call with x402 via _meta['x402/payment']."New value: +"Optional prepaid key (sk_scrapling_...) or catalog pass token (sdp_..., from pass_day/pass_month). Otherwise pay per call with x402 via _meta['x402/payment']."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely non-obvious behavior: it is a paid call ($0.005 USDC), precomputes from raw chain RPC (freshness/derivation source), and scopes to three chains. It omits any note on latency or what happens on an unsupported/fresh address.

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 paid cost and the core question, then a compact comma-delimited inventory of returned signals and the chain scope. No filler sentences; every clause carries a distinct fact.

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 must carry the return shape and it does so thoroughly (labels, score, balances, tx history, whale transfers). The one real gap is the behavior when 'chain' is omitted, since only 'address' is required.

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 67% and already documents address and api_key; the description restates the supported chains (ethereum, base, solana) which the enum already encodes. It adds no guidance on the optional api_key/payment path or on chain defaulting (chain is not required), so it does not compensate for the remaining coverage gap.

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?

Names a specific resource (a wallet) and enumerates the exact output taxonomy it returns: label (exchange/whale/active_trader/fresh_wallet/dormant), 0-100 activity score with reasons, balances, tx count, first/last activity, whale transfer history. That is far more specific than the sibling lookups (trader_wallet, counterparty_check) and lets an agent predict the payload before calling.

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?

Implicitly positions itself as a due-diligence / 'who is this address' lookup, but never states when to prefer it over siblings like trader_wallet, counterparty_check or address_poisoning, nor any exclusions. Usage is inferable from the output list but not spelled out.

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

All Scrapling x402 Data Store toolsInspect
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