Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Top Hyperliquid traders by PnL/ROI ($0.005)

top_traders
Read-only

PAID $0.005 USDC. Use when an agent asks who the most profitable crypto traders are or wants smart-money wallets to track/copy. Ranked from public Hyperliquid chain data (~47k accounts): address, PnL, ROI, volume, account value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_traders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNopnl|roi|volume|worst
limitNo
venueNo
windowNoday|week|month|allTime
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'].
min_accountNo

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 and openWorldHint=false, so the description's added value is the paid-call cost ($0.005 USDC), the provenance of the data (public Hyperliquid chain, ~47k accounts), and the shape of the result. It stops short of disclosing freshness/refresh cadence, pagination, or what happens if payment fails.

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?

Two tight sentences, price front-loaded, then the trigger condition, then data provenance and result fields. Nothing is wasted and nothing important is buried.

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 usefully enumerates the returned fields, and the price and data source cover the main unknowns for a paid read tool. It is slightly incomplete on parameter behavior and on how this differs from the free equivalent.

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 50%: sort, window and api_key have descriptions, while limit, venue and min_account are bare. The prose mentions volume and account value in passing but never explains how sort, window, venue, limit or min_account actually shape the ranking, so it does not compensate for the coverage gap. Baseline 3 is the ceiling here.

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?

States a specific resource (ranked Hyperliquid traders) plus the return fields (address, PnL, ROI, volume, account value) and the data source (~47k public accounts). It never names its near-duplicate sibling free_traders, so the agent cannot tell from the description alone why it should pay for this one.

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 concrete triggering condition: 'Use when an agent asks who the most profitable crypto traders are or wants smart-money wallets to track/copy.' That is clear positive guidance, but there are no exclusions or alternatives — notably no mention of the free tier (free_traders) or trader_wallet, which matters because this call costs $0.005.

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