Scrapling x402 Data Store

Polymarket odds search ($0.005)

lookup_polymarket

Read-only

PAID $0.005 USDC. Polymarket odds for an event: up to 10 markets matching a keyword with YES probability, 1h/24h/7d odds change, volume and liquidity. Examples: q=bitcoin, q=election. Refreshed about every 30 min.

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

Input Schema

Name	Required	Description	Default
`q`	Yes	Keyword(s) in the market question
`api_key`	No	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'].

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

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']."

AddedOct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only cover read-only and closed-world, so the description carries the real burden and delivers several non-obvious facts: a $0.005 USDC cost, a hard cap of 10 markets, and a ~30 min refresh cycle. Missing only edge behavior (empty result, stale-data warning), which keeps it off a 5.

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?

Three short sentences, front-loaded with the price and the resource, then the return shape, then examples, then freshness. Nothing is padding and the most decision-relevant fact (cost) leads.

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, and the description compensates by listing the returned fields and the result cap, so an agent knows what a call yields. Details like behavior on zero matches or truncation semantics are absent, which is the only real gap for a 2-param tool.

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?

Schema coverage is 100% so the baseline is 3, but the description goes further by framing q as keywords matched against the market question and giving two concrete sample values, which clarifies granularity better than the schema text alone.

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?

Names a specific resource (Polymarket odds for an event) and a specific verb-ish operation (keyword search returning matched markets), then enumerates the payload: YES probability, 1h/24h/7d change, volume, liquidity. No sibling in the list does prediction-market odds, so it is unambiguous.

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 examples (q=bitcoin, q=election) show how to phrase a query, which implies keyword-driven usage, but there is no explicit statement of when to pick this over the many free_* odds/price tools in the catalog, nor any exclusion. Usage is inferred rather than guided.

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.