Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Binance outflow snapshot per chain and asset ($0.02)

binance_flows
Read-only

PAID $0.02 USDC. Binance withdrawal-restart tracker: 1h and 24h inflow/outflow/net per chain (Ethereum, BSC, Base, Tron, Bitcoin) and per asset (USDT, USDC, WBTC/BTCB/BTC, ETH/WETH, native ETH/BNB/TRX) for Binance's publicly identified wallets (Binance's own published lists). USD via Chainlink with input timestamps; as-of time and block per chain; per-chain check states and spread_ok/max_spread_seconds.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false. The description adds useful context beyond annotations: the $0.02 cost, Chainlink-based USD pricing, as-of timestamps and block references, per-chain check states, and spread diagnostics, though it does not explain failure modes or data-refresh latency.

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?

It is front-loaded with the paid cost and then compactly specifies metrics, scope, and data-quality fields. The second sentence is dense and run-on, but every clause carries relevant information and there is no filler.

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 describe return content, and it does so by listing time windows, per-chain and per-asset metrics, as-of/block fields, and spread checks. It could better explain how to interpret 'withdrawal-restart' and the check states, but it is broadly complete for selection.

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?

The only parameter, api_key, is fully documented in the schema, including prepaid-key and pass-token alternatives. The description adds no further meaning about this parameter, so the schema carries the full burden and the baseline 3 is appropriate.

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 (Binance withdrawal-restart tracker) and enumerates the exact metrics, chains, assets, and wallet scope returned. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like free_binance_flows or binance_flows_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says the tool is paid and mentions payment options only indirectly, but gives no explicit when-to-use guidance, prerequisites, or comparison with the free and report sibling tools. An agent must infer that this is the premium snapshot variant.

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