Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

Odds research pulse + Fear & Greed ($0.005)

odds_pulse
Read-only

PAID $0.005. Thin derived Polymarket matches for q= plus Fear & Greed. Informational only — not investment advice. No Kalshi.

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

Input Schema

NameRequiredDescriptionDefault
qYes
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. Added

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already cover the safety profile, so the description's main added value is the $0.005 price and the 'derived/thin' data-quality hint. It does not explain what 'thin' actually means (coverage, staleness, match quality) or any rate/call limits, which matters for a paid call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Telegraphic but front-loaded: price and the two data components come first, disclaimer last. Every fragment carries information, though the fragmentary style ('Thin derived ... for q=') borders on terse jargon.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a barely-documented q, the description should at least sketch what comes back (match fields, Fear & Greed scale). It names the two data components, which is enough to identify the call, but leaves return shape and match quality undefined.

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 50%: api_key is documented in the schema, but q is described nowhere. The description implies q is a matching term over Polymarket markets, which adds some meaning beyond the schema, but gives no format, matching rules, or example values.

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?

Names the resource and scope concretely: Polymarket matches selected by a query plus a Fear & Greed reading, and 'No Kalshi' bounds the data source. It falls short of 5 because it never distinguishes this 'thin derived' pulse from siblings like odds_history, odds_movers, or odds_hypothesis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance relative to alternatives. 'No Kalshi' and 'Informational only' are scope/disclaimer statements, not usage routing, so an agent must guess when this cheap pulse is the right pick over the other odds tools.

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