Skip to main content
Glama
Sign In

Scrapling x402 Data Store

by io.github.bnth09productions-maker
OverviewDiscussionsAdmin

24-hour catalog pass ($2)

pass_day
Read-only

PAID $2 USDC once. Returns a pass_token (sdp_...) that unlocks every paid lookup priced up to $1/call for 24h (60 calls/min, 1500/UTC day). Pass it as api_key on later tool calls. Shown once.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior2/5

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

The disclosure itself is strong — price ($2 USDC, paid once), token prefix, 24h validity, rate caps (60/min, 1500/UTC day) and the critical "Shown once" irreversibility warning. However, this conflicts with the readOnlyHint=true annotation: an agent trusting that hint would treat a $2 irreversible charge that issues and persists an entitlement as a free, safe read, which materially misrepresents the side effect.

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?

Four dense sentences, front-loaded with the cost and the deliverable, followed by scope, limits, and the one-time visibility warning. Nothing is redundant and no sentence could be dropped without losing operational information.

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 carries the return-value burden and does so well (token prefix, shown once). It is nearly complete for a purchase tool, but omits the payment mechanics (x402 / _meta), what happens on insufficient funds, and any stacking/refund behavior.

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 adds real meaning by linking the tool's output (the sdp_ token) to the api_key parameter used on later calls, which the schema text alone does not connect. Minor uplift above baseline is warranted.

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 precise verb+resource+price: buy a 24h catalog pass for $2 USDC and receive an sdp_ token that unlocks paid lookups up to $1/call. The only gap is that the sibling pass_month is never named or contrasted, so an agent cannot tell from the description alone which pass duration to buy (it only appears incidentally in the api_key schema text).

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?

"Pass it as api_key on later tool calls" gives clear downstream usage of the returned token, but there is no guidance on when to buy this rather than pass_month or paying per call via x402, and no stated precondition (e.g. expected call volume). Usage is implied rather than directed.

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