Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Whole-market bundle ($0.001)

market_pulse
Read-only

PAID $0.001 USDC. Whole crypto market in one call: top 10 coins by rank (Chainlink prices), top volume leaders, top DeFi protocols by TVL, DEX volume leaders and total, and DeFi heatmap highlights (biggest sectors, 1d gainers and losers). No parameters. No charge if sources are unavailable.

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

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

A4/5.0
Behavior4/5

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

Annotations cover the read-only and closed-world profile, and the description adds genuinely new operational context: a $0.001 USDC cost, x402 payment or prepaid key paths, and a no-charge guarantee when sources are unavailable. It stops short of describing rate limits or the shape of the aggregated response, but the payment and failure semantics are the key unknowns for a paid tool and they are stated.

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?

The price is front-loaded in capitals, followed by a single dense sentence listing the bundled datasets, then two short qualifiers about parameters and billing. Every clause carries information, though the enumeration is long enough that it verges on a run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return contents, and it does so explicitly by naming all five data blocks. Combined with the payment and failure terms, an agent has everything needed to decide to call it and to interpret the result.

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 100%, so the api_key parameter, its accepted prefixes, and the x402 fallback are already fully documented in the schema. The description's 'No parameters' is shorthand for no required inputs and adds no meaning about api_key beyond what the schema provides; 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?

The description names a specific resource and enumerates its exact contents: top 10 coins by rank via Chainlink, volume leaders, DeFi protocols by TVL, DEX volume leaders and total, and heatmap highlights. This lets an agent distinguish it from siblings like free_crypto_top10 or defi_intel without opening 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 Guidelines3/5

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

Usage is only implied: the 'whole market in one call' framing suggests it substitutes for several narrower tools, and 'No parameters' signals it is a zero-config call. However, it never names an alternative or states when to pick this bundle over free_crypto_top10, free_defi_top_yields, or defi_intel, which matters given the many free siblings.

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