Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Coin price lookup ($0.001)

lookup_coin
Read-only

PAID $0.001 USDC. Current BTC, ETH and ~155 major coin prices from Chainlink on-chain feeds: USD price, 1h/24h/7d/30d change and 24h high/low (no market cap or volume). Examples: q=btc, q=ethereum. Refreshed about every 30 min, answers in under 100 ms. Unknown coin returns an error with no charge.

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": {
      "q": "<q>"
    },
    "name": "lookup_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSymbol (btc), coin id (bitcoin) or name
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. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Symbol (btc), CoinGecko id (bitcoin) or name"New value: +"Symbol (btc), coin id (bitcoin) or name"
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the $0.001 USDC cost, the ~30-minute refresh cadence, sub-100ms latency, that unknown coins error with no charge, and what is deliberately excluded (no market cap or volume). This is exactly the context an agent needs to decide and to set expectations.

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?

Front-loads the price and payment model, then data coverage, then examples, then performance/error behavior. Every clause carries distinct information with no repetition.

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?

With no output schema, the description steps in to enumerate the returned fields (USD price, 1h/24h/7d/30d change, 24h high/low), and it covers payment/auth indirectly via the schema's api_key note. Nothing material for correct invocation is missing.

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 both q and api_key are already documented structurally. The description reinforces the accepted input forms with examples (q=btc, q=ethereum) but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 verb and resource ('Current BTC, ETH and ~155 major coin prices from Chainlink on-chain feeds') plus the exact data fields returned. It is precise about scope but never names or contrasts with siblings like free_prices, prices or free_crypto_top10, so an agent must infer which price tool to pick.

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?

The description implies when it applies (current spot price plus multi-horizon change) and notes the paid nature, but gives no explicit 'use this instead of X' guidance despite several overlapping siblings (free_prices, prices, price_moves). The unknown-coin error behavior is useful but is not usage routing.

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