Scrapling x402 Data Store

Live feed catalog (free)

free_feeds

Read-only

FREE. Catalog of every live feed, refreshed about every 30 min (crypto, DeFi, Polymarket, stocks, new pools, token risk) with row counts, freshness and full price, plus the paid single-lookup tools and their prices.

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_feeds"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), yet the description adds genuinely useful context: a ~30-minute refresh cadence and the per-row contents (row counts, freshness, full price). It does not state rate limits or auth needs, which is a minor gap.

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?

A single dense sentence that front-loads the crucial 'FREE' marker and then layers coverage, refresh cadence, and return contents with no filler.

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?

With no output schema, the description must convey what comes back, and it does (categories, row counts, freshness, price, plus paid tool listings). It is sufficient for a zero-param discovery call, though it could be slightly clearer about the response shape (e.g. a list of feeds).

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 tool takes zero parameters, so the baseline for a no-arg definition applies; there is nothing for the description to disambiguate. No parameter semantics are needed or missing.

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 ('catalog of every live feed') and enumerates what it covers (crypto, DeFi, Polymarket, stocks, new pools, token risk), making it clearly a discovery tool rather than a single-value lookup. Sibling differentiation is strong by implication (this is the browse/index counterpart to lookup_* tools), but 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The framing as a catalog with prices implies you call it to discover what feeds/tools exist before doing a lookup, but there is no explicit when-to-use, when-not-to-use, or named alternative. The 'paid single-lookup tools' mention hints at the contrast without stating it.

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 tools Inspect

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.