Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Up to 3 token prices, on-chain (free)

free_prices
Read-only

FREE. Up to 3 token prices in USD (btc,eth,sol by default) from Chainlink oracles read on-chain, with feed, chain and block. prices ($0.003) takes up to 50 tokens.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 safety is covered. The description adds useful behavioral context beyond annotations: the data source is Chainlink oracles read on-chain, the default token set is btc/eth/sol, and the response includes feed, chain, and block.

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 two compact sentences with zero waste. The most important constraint, FREE up to 3 tokens, is front-loaded, and the paid alternative is mentioned immediately afterward.

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 zero-parameter, read-only tool with no output schema, the description provides enough context to call it correctly: it states the free limit, default tokens, oracle source, and key return fields. It could be slightly more complete with rate-limit or error behavior, but nothing critical is missing.

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

Parameters4/5

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

The input schema has zero parameters, so the baseline is 4. The description notes the default btc/eth/sol token set and the free 3-token limit, which is consistent with a no-parameter tool even though it does not explain how or whether token selection is possible.

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 states a specific resource and scope: up to 3 token prices in USD, defaulting to btc/eth/sol, sourced from Chainlink oracles read on-chain. It also names the returned fields (feed, chain, block), which clearly distinguishes it from the paid sibling `prices`.

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?

It clearly frames this as the FREE option limited to 3 tokens and explicitly contrasts it with `prices ($0.003)`, which takes up to 50 tokens. The when-to-use routing is clear, though it does not explicitly say what to do if the user needs more than 3 tokens or mention other price-related 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