Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Bulk token prices, up to 50 per call ($0.003)

prices
Read-only

PAID $0.003 USDC. Up to 50 crypto token prices in USD in one call from Chainlink Data Feeds read on-chain (Ethereum, Arbitrum, Base): price, feed address, chain, oracle update time, block number. Unknown symbols listed in not_found.

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": {
      "tokens": "<tokens>"
    },
    "name": "prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
vsNousd
tokensYesComma-separated symbols, max 50, e.g. btc,eth,sol,link
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds important behavioral context: it costs $0.003 USDC, reads Chainlink Data Feeds on-chain across three chains, returns specific fields, and reports unknown symbols in not_found. It does not detail payment mechanics or error handling beyond not_found, but adds substantial value.

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?

The description is a compact, front-loaded sentence with no wasted words. Cost, scope, source, return fields, and not_found behavior are all packed efficiently into one dense statement.

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?

There is no output schema, but the description compensates by enumerating return fields (price, feed address, chain, oracle update time, block number) and the not_found behavior. It is nearly complete for an agent to call and interpret results, with only payload structure details 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 description coverage is 100%, so all three parameters are already well documented. The description reinforces the max-50 token constraint and mentions not_found, but does not add syntax or format details beyond the schema.

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?

The description clearly states a bulk price-fetching operation with scope (up to 50 tokens), source (Chainlink Data Feeds on Ethereum, Arbitrum, Base), and result fields. It implies paid vs free through the opening cost note, but does not explicitly name or differentiate from sibling tools like free_prices or lookup_coin.

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 gives practical constraints (paid, up to 50 per call) that imply when this tool is appropriate over single-token or free alternatives. However, it does not explicitly say when to choose this over free_prices, lookup_coin, or price_moves, leaving comparison 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