Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Small/meme token price + volume history ($0.01)

meme_history
Read-only

PAID $0.01 USDC. Use when an agent needs a price/volume chart or back-data for a small-cap or meme token on Base, BNB Chain or pump.fun. ~15-min snapshots kept 30 days with high/low/change summary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "meme_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
hoursNo
tokenYes
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 safety (readOnlyHint=true, openWorldHint=false), so the description's job is additive context — and it delivers: $0.01 USDC cost, ~15-minute snapshot granularity, 30-day retention, and the shape of the summary (high/low/change). It does not mention rate limits, failure/empty-result behavior for unknown tokens, or pagination limits on long ranges.

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?

Three tight sentences, cost and use case front-loaded, then granularity and retention. No repetition of the title and nothing that could be cut without losing information.

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?

For a 4-parameter read-only tool with no output schema, the description supplies cost, data granularity, retention window, supported chains, and a summary of return contents. The remaining gap is parameter-level detail (hours limits, token identifier format), which the low-coverage schema does not fill in.

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 25% — essentially just api_key is documented — so the description must carry the rest. It partially compensates by naming the supported chains (Base, BNB Chain, pump.fun) and implying a historical range via the 30-day retention note, but 'token' format (address vs symbol), 'hours' bounds/default, and the base/bsc/solana mapping are left unexplained.

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 (price/volume history) with a clear scope qualifier: small-cap or meme tokens on Base, BNB Chain or pump.fun. That distinguishes it implicitly from live-price siblings like prices/free_prices and discovery siblings like meme_trending, though no sibling is named explicitly.

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?

The opening 'Use when an agent needs a price/volume chart or back-data...' gives a clear triggering condition and narrows it to small-cap/meme tokens and three chains. It stops short of explicit exclusions (e.g. 'for majors use prices', 'for discovery use meme_trending'), leaving some routing inference 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