Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Binance outflow report: biggest withdrawals and destinations ($0.25)

binance_flows_report
Read-only

PAID $0.25 USDC. Everything in binance_flows plus the biggest single withdrawals in 24h (tx hash, block, time, USD, recipient), destination labels where identifiable (other exchanges, bridges, else unlabeled), destination breakdown, hourly net-flow series and the tracked wallet list with sources.

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

Input Schema

NameRequiredDescriptionDefault
limitNobiggest withdrawals to list, 1-100, default 25
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.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description adds real context: the call is billed at $0.25 USDC and the result is a richer superset of the free feed. It doesn't mention freshness guarantees, rate limits, or what happens when payment is absent, keeping it short of a 5.

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?

A single sentence with the price front-loaded followed by a dense enumeration of deliverables; nearly every clause earns its place. It is a long run-on list, which costs a point on readability, but nothing is wasted.

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 enumerate return contents, and it does so thoroughly (withdrawals, labels, breakdown, hourly series, wallet list). For a zero-required-param read tool this is close to complete; only the shape/ordering of the breakdown and series is left unspecified.

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 description coverage is 100%, with `limit` (1-100, default 25) and `api_key`/x402 payment flow fully documented in the schema. The description adds nothing about parameters, so the baseline 3 applies.

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 resource (Binance outflow data) and enumerates exactly what this report contains beyond the base feed: biggest withdrawals with tx hash/block/time/USD/recipient, destination labels, breakdown, hourly net-flow series, tracked wallet list. The phrase 'Everything in binance_flows plus...' explicitly positions it against the sibling binance_flows/free_binance_flows, so an agent can distinguish it without opening another schema.

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?

Naming binance_flows as the subset implies when to upgrade (need recipient-level detail or hourly series), and the '$0.25' signals a paid tier. But there is no explicit 'use free_binance_flows when…' rule and no stated prerequisites or cost trade-off guidance; usage must be inferred.

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