Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Trending meme coins + risk verdict ($0.005)

meme_trending
Read-only

PAID $0.005 USDC. Use when an agent asks what meme coins are trending/pumping on Base, BNB Chain (bsc) or Solana pump.fun. Ranked by volume x spike: price, change, buys/sells, liquidity, pool age, go/caution/avoid verdict. From on-chain swap logs.

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

Input Schema

NameRequiredDescriptionDefault
chainNo
limitNo
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'].
min_liquidityNo

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

B3.4/5.0
Behavior4/5

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

Adds real context beyond annotations: it is a paid call ($0.005 USDC via x402), accepts a prepaid sk_scrapling_ key or sdp_ pass token, and derives rankings from on-chain swap logs. That payment/auth model is exactly what annotations (readOnlyHint, openWorldHint) do not convey. It stops short of noting rate limits or what happens when no payment is supplied.

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?

Dense and front-loaded: price first, then trigger condition, then ranking logic, then returned fields. Telegraphic phrasing ("volume x spike", "go/caution/avoid") costs a little readability but no sentence is wasted.

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

Completeness3/5

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

Discloses the returned metrics (price, change, buys/sells, liquidity, pool age, verdict), which substitutes for a missing output schema. However, for a 5-parameter tool with 20% schema coverage and no defaults declared, key operational details such as default chain, default window, and limit behavior are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description needs to compensate for chain, limit, window, and min_liquidity, and it does not. The chain values are already in the enum, and nothing explains units, defaults, or tradeoffs for window, limit, or minimum-liquidity filtering.

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 and scope: trending/pumping meme coins on Base, BSC or Solana pump.fun, ranked by volume x spike. Precise enough to know what it returns, but it never distinguishes itself from close siblings such as free_meme_trending, meme_new_pools or pumpfun_feed.

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?

"Use when an agent asks what meme coins are trending/pumping" gives a clear trigger, but there is no guidance on when NOT to use it. Most notably it is silent about the free_meme_trending sibling and about how it differs from meme_new_pools or meme_history, so the paid-vs-free routing decision is left to the agent.

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