Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Price move alerts ($0.002)

price_moves
Read-only

PAID $0.002 USDC. Coins (~155 Chainlink-priced) whose price moved more than threshold % (default 5) over 1h and/or 24h, biggest first, plus DeFi protocols whose TVL moved more than threshold in 1d. Built for polling. Empty list is a valid answer.

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

Input Schema

NameRequiredDescriptionDefault
windowNo
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'].
directionNo
thresholdNo
include_defiNo

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.4/5.0
Behavior5/5

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

Annotations only cover readOnly and open-world hints; the description adds the paid cost ($0.002 USDC), result ordering ('biggest first'), the valid-empty-result case, the ~155-coin coverage and the Chainlink pricing source. Those are exactly the traits an agent can't infer from structured fields and that matter for budgeting and for interpreting an empty response.

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?

Cost is front-loaded in two words, then the payload description, then the polling/interaction notes. Four sentences, each carrying distinct information with no filler or restatement of the schema.

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 does the right work by sketching the payload (coins + DeFi TVL movers, ordered), but gaps remain for a 5-param tool: direction semantics and per-param defaults are missing, and the response field shape is only implied.

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 only 20% (just api_key), so the description carries most of the burden. It supplies the threshold default (5), the 1h/24h window semantics and what include_defi adds, but the 'direction' enum (up/down/both) is never explained and no defaults are given for window/direction/include_defi.

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 noun with scope and data source: 'Coins (~155 Chainlink-priced) whose price moved more than threshold % over 1h and/or 24h, plus DeFi protocols whose TVL moved more than threshold in 1d.' This clearly separates it from siblings like prices/free_prices (snapshot quotes) and whale_moves (wallet flows) without needing to open a schema.

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?

'Built for polling' gives an explicit usage context, and the paid-call notice sets cost expectations before invocation. It stops short of naming an alternative (e.g., free_prices or free_alerts_info) or stating when NOT to use it, so there is no exclusion guidance.

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